01366 – Opened due to crash signal (Audi)

Audi-specific code — factory diagnostic data

01366 means the Audi TT central locking system opened or disabled a function after receiving a crash signal. In plain terms, you may notice door lock behavior changes, remote locking issues, or convenience features that stop working until you diagnose the stored fault. According to Audi factory diagnostic data, this manufacturer-specific code means Opened due to crash signal. That wording matters. It does not prove a bad lock module. It tells you the 35-Central Locking Control Module saw a crash-related input or status and reacted by opening or unlocking part of the system logic. On Audi platforms, that condition can result from a real crash event, a stored crash status, wiring trouble, or incorrect module communication.

01366 Quick Answer

On Audi vehicles, 01366 means the 35-Central Locking Control Module registered an Opened due to crash signal condition. Diagnose the crash-related input, stored event status, and module communication before replacing any locking parts.

What Does 01366 Mean?

The official Audi definition is Opened due to crash signal. In practice, the central locking module detected a crash-related command or status and changed system operation in response. That can affect locking, unlocking, remote convenience functions, or system readiness after an impact event or a false trigger.

Technically, the module is not identifying a failed door latch by this code alone. It is identifying a trouble area tied to a crash input or crash status path. If your scan data includes the FTB subtype -035, treat that as subtype information only. On this platform, it points you toward a highly specific diagnostic direction, not an automatic parts verdict. The key job now is to confirm whether the crash signal was valid, latched in another module, or corrupted by wiring, power supply, ground, or network issues.

Theory of Operation

Under normal conditions, the Audi TT central locking module manages door locks, remote functions, and convenience logic. It also reacts to safety-related inputs from other vehicle systems. When the car registers a crash event, the vehicle may command unlocking or open selected locking logic to support occupant exit and emergency access.

This code sets when that crash-related condition reaches the central locking module and the module records that it opened due to the signal. The fault can appear after a real impact. It can also appear when another module holds a crash status, when wiring carries the wrong signal, or when communication faults make the central locking module think a crash event occurred. That distinction drives the diagnosis.

Symptoms

Symptoms usually affect body convenience functions more than engine performance.

• Locking behavior: Doors may unlock unexpectedly, stay unlocked, or refuse normal remote locking.
• Remote response: The key fob may work inconsistently after the crash-related status sets.
• Central locking faults: The Audi TT may store central locking faults without a clear latch or actuator failure.
• Convenience function changes: Interior convenience features tied to locking status may act abnormally.
• Stored crash-related codes: Other modules may hold crash event or communication faults at the same time.
• Intermittent operation: The problem may appear only after battery disconnects, module wake-up, or repeated lock commands.
• No obvious mechanical failure: Door latches can test fine even though 01366 remains stored.

Common Causes

• Crash signal input triggered by another module: The central locking module stores 01366 when it receives a crash-related opening command from the Audi safety logic.
• Stored event after collision or impact: A prior impact event can leave the fault stored even after body repairs, battery replacement, or central locking concerns appear resolved.
• Intermittent open circuit in the crash signal path: A loose terminal, broken conductor, or damaged splice can interrupt the signal circuit and set the code with FTB -035, which identifies an open-circuit fault subtype.
• Corrosion at module or harness connectors: Corrosion raises resistance and can break the crash signal path long enough for the central locking control module to log the fault.
• Water intrusion in the Audi TT interior harness area: Moisture can damage terminals or wiring near the central locking module and create intermittent opens or false crash-signal status changes.
• Poor module power or ground quality: Voltage loss at the central locking module can corrupt input interpretation and make the module register a crash-related opening event incorrectly.
• Aftermarket alarm or locking system wiring damage: Non-OEM splices often disturb the lock control circuits and can interrupt the signal path the module uses to monitor crash-triggered unlocking.
• Fault in a related safety or convenience control unit: If another Audi module sends an incorrect crash-status message or output, the central locking module may store 01366 even though the lock hardware still works.

Diagnosis Steps

Use a factory-capable scan tool, a wiring diagram, a DVOM, and a test light or loaded circuit tester. You also need access to Audi module data and connector views. For this circuit-type fault, freeze frame review should focus on battery voltage, ignition state, and any related safety or convenience module DTCs. Freeze frame shows when the code set. A scan tool snapshot helps catch intermittent faults during wiggle or road tests.

1. Confirm 01366 in the 35-Central Locking Control Module and record all stored and related DTCs. Save freeze frame data, especially battery voltage, ignition state, and any companion faults in safety, convenience, or airbag-related modules. Note whether the code returns immediately at key-on. A hard CCM fault often returns right away.
2. Check the relevant fuses and power distribution first. Inspect the visible circuit path before any meter work, including harness routing, prior repairs, aftermarket alarm splices, and signs of impact or water entry in the Audi TT. If the scan tool can access related modules, check whether any module reports a crash event or crash-signal fault.
3. Verify central locking module power and ground under load. Do not rely on unloaded voltage or simple continuity checks. Perform voltage-drop testing with the circuit operating. Ground drop should stay below 0.1 volt under load. A weak ground can show full battery voltage with no load and fail only when current flows.
4. Inspect the central locking module connector, the crash-signal input path, and any intermediate connectors or splices. Look for spread terminals, backed-out pins, green corrosion, moisture tracks, and broken insulation. Pay close attention to areas where the Audi TT harness flexes or sits low in the body.
5. Clear the code and cycle the ignition. Then watch live data or status blocks for crash-signal status, central locking status, and related input states if the scan tool supports them. Compare the displayed status with the actual vehicle condition. If the status changes during harness movement, you likely found an intermittent open.
6. Perform targeted circuit tests on the crash-signal path using the wiring diagram. Check the signal wire end to end for an open under loaded conditions, not just static continuity. If the circuit uses a switched input from another module, verify that source output and the path to the central locking module. If the platform uses networked crash information instead of a direct wire, confirm the related module reports normal status and no communication faults.
7. Inspect for water intrusion and collision-repair damage in the convenience module area and along the interior harness. Audi locking modules often suffer from moisture-related terminal damage. Dry, clean, and repair affected connectors before condemning any control unit.
8. If you find an intermittent fault, use a scan tool snapshot during a wiggle test or road test. Freeze frame captured the original set conditions automatically. The snapshot captures live data when the concern happens again. That distinction matters when the code sets only during vibration, door movement, or low-voltage events.
9. Only after the circuit, powers, grounds, and related module inputs test correctly should you evaluate the central locking module itself. If the crash-signal input remains implausible with a verified good circuit and valid source signal, follow Audi service information for module evaluation, coding, and adaptation checks.
10. After repairs, clear all codes and run multiple key cycles. Recheck the central locking module and all related modules. Confirm the fault does not return immediately or after harness movement, locking operation, or a road test. Make sure no related convenience or safety code resets.

Professional tip: FTB -035 gives you useful direction here. Treat it as an open-circuit subtype, not a parts verdict. On this Audi fault, technicians waste time replacing lock actuators because the doors may unlock oddly. The smarter path starts with the crash-signal circuit, module power and ground quality, and any evidence of water intrusion or prior repair work.

Possible Fixes

• Repair the open in the crash-signal circuit: Fix the broken wire, poor splice, or terminal tension problem only after loaded circuit testing confirms the fault location.
• Clean and restore corroded connectors: Remove corrosion, repair damaged terminals, and protect the connection if moisture caused high resistance or an intermittent open.
• Correct power or ground faults at the central locking module: Restore fuse feed, ground integrity, or power distribution issues when voltage-drop testing proves the module supply path is weak.
• Remove or repair aftermarket wiring damage: Restore the Audi TT locking and convenience wiring to proper configuration if an alarm or remote-entry add-on disturbed the circuit.
• Repair water intrusion damage: Eliminate the leak source and repair affected harness or connector sections if moisture has compromised the module area.
• Address the related source module fault: Repair the upstream safety or convenience module issue if testing shows it sends an incorrect crash-related signal to the central locking module.
• Replace and code the central locking module only after verification: Consider module replacement only when wiring, inputs, outputs, power, ground, and related module logic all test good.

Can I Still Drive With 01366?

You can usually drive an Audi TT with 01366 if the car starts, locks, unlocks, and shows no crash-related warning behavior. This code sits in the 35-Central Locking Control Module, not in the engine controller. That means it usually affects convenience functions more than drivability. Still, do not ignore it. The central locking module may have received a crash signal command that triggered an unlock or shutoff routine, or it may see that signal circuit in an implausible state. If the fault remains active, door locking behavior can become unpredictable. Confirm basic latch operation, remote locking, and interior lock switch response before regular use. If the car shows other crash-event faults, water intrusion, or widespread electrical issues, stop and diagnose the network and power supply first.

How Serious Is This Code?

In most cases, 01366 is a moderate fault and an operational inconvenience, not an immediate drivability failure. The code means the Audi central locking module recorded an opened due to crash signal condition. If the scan data includes FTB suffix -035, treat that suffix as subtype information only. It helps narrow the fault path, but it does not name a failed part. On this platform, the issue often matters most when the locks, alarm logic, or convenience functions stop behaving normally after a battery event, module reset, crash history, or wiring fault. The seriousness increases if the doors will not lock, if the alarm triggers falsely, or if multiple control modules show communication or crash-related codes together. That pattern can point to wiring damage, low system voltage history, module water damage, or a fault in the signal path between safety-related and convenience-related modules. Diagnose it promptly, especially if the TT has intermittent electrical symptoms.

Common Misdiagnoses

Technicians often replace the central locking module too early. That mistake happens when they read the text description and assume the module failed internally. The wording does not prove that. It only identifies the trouble area the module recognized. Another common error is treating 01366 like a current crash event without checking whether the code stored after a past incident, low voltage episode, or connector disturbance. Some shops also ignore the FTB subtype and skip basic circuit checks. On Audi systems, corrosion at module connectors, weak grounds, water intrusion, and disturbed harness routing cause this code more often than a hard module failure. Avoid wasted spending by checking scan tool status, freeze-frame context if available, module power and ground integrity, latch and lock operation, and any companion faults in comfort, convenience, or crash-related modules before authorizing parts.

Most Likely Fix

The most common repair direction is correcting the signal or support issue that made the 35-Central Locking Control Module register an opened due to crash signal condition. That usually means repairing connector corrosion, restoring clean power and ground to the Audi convenience module, fixing damaged wiring in the crash-signal path, or correcting water intrusion damage in the module area. In some cases, technicians clear the code only after they verify normal live data, normal lock operation, and no returning companion faults across related modules. Module replacement ranks lower on the list. Use it only after you verify powers, grounds, network integrity, and input behavior. After repair, operate the locks through all switch and remote commands, then drive and key-cycle the vehicle long enough for the module self-checks to run. Enable criteria vary by platform, so confirm the final verification routine in Audi service information.

Repair Costs

Repair cost depends on whether the confirmed root cause is wiring, connector condition, a sensor, a module, or the labor needed to diagnose the fault correctly.