2022 LINCOLN NAUTILUS — Problems, Recalls & Safety Data

The contact owns a 2022 Lincoln Nautilus. The contact stated that while another person was driving approximately 15-50 MPH, the vehicle sputtered and jerked. The vehicle was driven to the workplace, and the contact attempted to test-drive the vehicle. The contact stated that upon starting the vehicle and shifting to drive, there was delay while responding, with a clunking sound coming from the vehicle. The contact stated that the vehicle failed to shift into gear the following day. The contact stated that upon shifting to reverse, the vehicle jerked forward, and upon shifting to park(P), there was a delay before the vehicle responded. There was a delay after shifting out of park(P). There was no warning light illuminated. The vehicle was towed to the dealer, where several internal diagnostic trouble codes were found. The dealer determined that the transmission had failed and needed to be replaced. The contact related the failure to NHTSA Campaign Number: 22V413000 (Power Train). The vehicle was not repaired. The manufacturer was notified of the failure, but no assistance was provided because the VIN was not included in the recall. The failure mileage was approximately 149,200.

There is a class action lawsuit for the 2019-2021 Nautilus with the 8F35 transmission, which is the same transmission that my 2022 Nautilus has. Ford has also issued multiple technical service bulletins (25-2154, 21-2389) regarding the 8F35 transmission. My transmission has had a catastrophic failure and began slipping out of gear while driving on the highway. The vehicle lost power several times while driving. The wrench light came on. I was able to make it to the dealership where they are quoting me for a total replacement of the transmission. One week prior, I brought the vehicle in to reprogram the PCM due to a recall alert I got from the Lincoln app. I was experiencing jerking and shuddering prior to the PCM reprogram, then within days of the reprogramming, the transmission completely failed.

Submitted by: [XXX] Dealership: Joe Rizza Ford of Orland Park Vehicle: 2021 Lincoln Nautilus VIN: [XXX] Date: 04/04/25 Overview: Vehicle VIN [XXX] has shown persistent signs of remote system manipulation, unauthorized firmware behavior, and OTA event spoofing. These symptoms have manifested in repeated diagnostic trouble codes (DTCs) across key modules, backdated OTA logging activity, and anomalous file sizes inconsistent with Ford’s documented OTA campaigns. Additionally, the vehicle owner has experienced personal harm attributed to the manipulation: numbness in the back, significant financial and mental distress, and deterioration in relationships with family members, which all correlate with the suspected interference and systemic issues. Key Findings: RFA (Remote Function Actuator) Module Behavior: Repeated DTCs across antennas #2, #3, #4, #6, #8, #11, and #12. Frequent B1B59:87 (BLE Low Energy Module fault) — indicates repeated Bluetooth stack failure or interference. U200F:00 Control Module Output Power C faults consistently recorded. GWM (Gateway Module A) and TCU (Telematics Control Unit) Logs: Software package inconsistencies including large firmware blocks (176 MB to 764 MB). Mismatched "Current Software" vs. "Available Software" versions. Cloud/server-pushed updates logged without dealership-initiated campaign. Confirmed campaign expired for firmware block logged on January 27, 2025, raising further questions on the legitimacy of update triggers. OTAM (Over-The-Air Manager) Log Red Flags: Entries showing timestamps such as January 3, 2000 and January 1, 2018. Consent flags spoofed: "sourceOfConsent='User(1)'" Trigger expiration hours preset to "336" (14-day OTA window, commonly used in timed malware execution) Absence of release notes or authorized campaign identifiers. Pattern Confirmation: Activity spikes on: [XXX], [XXX], and [XXX]. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Submitted by: [XXX] Dealership: Joe Rizza Ford of Orland Park Vehicle: 2021 Lincoln Nautilus VIN: [XXX] Date: 04/04/25 Overview: Vehicle VIN [XXX] has shown persistent signs of remote system manipulation, unauthorized firmware behavior, and OTA event spoofing. These symptoms have manifested in repeated diagnostic trouble codes (DTCs) across key modules, backdated OTA logging activity, and anomalous file sizes inconsistent with Ford’s documented OTA campaigns. Additionally, the vehicle owner has experienced personal harm attributed to the manipulation: numbness in the back, significant financial and mental distress, and deterioration in relationships with family members, which all correlate with the suspected interference and systemic issues. Key Findings: RFA (Remote Function Actuator) Module Behavior: Repeated DTCs across antennas #2, #3, #4, #6, #8, #11, and #12. Frequent B1B59:87 (BLE Low Energy Module fault) — indicates repeated Bluetooth stack failure or interference. U200F:00 Control Module Output Power C faults consistently recorded. GWM (Gateway Module A) and TCU (Telematics Control Unit) Logs: Software package inconsistencies including large firmware blocks (176 MB to 764 MB). Mismatched "Current Software" vs. "Available Software" versions. Cloud/server-pushed updates logged without dealership-initiated campaign. Confirmed campaign expired for firmware block logged on January 27, 2025, raising further questions on the legitimacy of update triggers. OTAM (Over-The-Air Manager) Log Red Flags: Entries showing timestamps such as January 3, 2000 and January 1, 2018. Consent flags spoofed: "sourceOfConsent='User(1)'" Trigger expiration hours preset to "336" (14-day OTA window, commonly used in timed malware execution) Absence of release notes or authorized campaign identifiers. Pattern Confirmation: Activity spikes on: [XXX], [XXX], and [XXX]. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Submitted by: [XXX] Dealership: Joe Rizza Ford of Orland Park Vehicle: 2021 Lincoln Nautilus VIN: [XXX] Date: 04/04/25 Overview: Vehicle VIN [XXX] has shown persistent signs of remote system manipulation, unauthorized firmware behavior, and OTA event spoofing. These symptoms have manifested in repeated diagnostic trouble codes (DTCs) across key modules, backdated OTA logging activity, and anomalous file sizes inconsistent with Ford’s documented OTA campaigns. Additionally, the vehicle owner has experienced personal harm attributed to the manipulation: numbness in the back, significant financial and mental distress, and deterioration in relationships with family members, which all correlate with the suspected interference and systemic issues. Key Findings: RFA (Remote Function Actuator) Module Behavior: Repeated DTCs across antennas #2, #3, #4, #6, #8, #11, and #12. Frequent B1B59:87 (BLE Low Energy Module fault) — indicates repeated Bluetooth stack failure or interference. U200F:00 Control Module Output Power C faults consistently recorded. GWM (Gateway Module A) and TCU (Telematics Control Unit) Logs: Software package inconsistencies including large firmware blocks (176 MB to 764 MB). Mismatched "Current Software" vs. "Available Software" versions. Cloud/server-pushed updates logged without dealership-initiated campaign. Confirmed campaign expired for firmware block logged on January 27, 2025, raising further questions on the legitimacy of update triggers. OTAM (Over-The-Air Manager) Log Red Flags: Entries showing timestamps such as January 3, 2000 and January 1, 2018. Consent flags spoofed: "sourceOfConsent='User(1)'" Trigger expiration hours preset to "336" (14-day OTA window, commonly used in timed malware execution) Absence of release notes or authorized campaign identifiers. Pattern Confirmation: Activity spikes on: [XXX], [XXX], and [XXX]. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)