Envoy Air Flight 3936
Embraer ERJ 170-100 LR · Incident: wrong surface or wrong airport during landing
From Norfolk, VA to an unrecorded destination
Event
- NTSB case
- DCA24LA318
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Embraer ERJ 170-100 LR
- Aircraft type
- Embraer ERJ-170
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N772MR
- Operator
- Envoy Air
- Onboard fatalities
- Unknown
- Route
- From Norfolk, VATo not recorded
- Aircraft age
- About 20 years (built 2004)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Wrong surface or wrong airport
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
This incident occurred when the flight crew of Envoy Airlines flight 3936 (ENY3936), an Embraer 170-100 LR, was cleared for a visual approach to land on runway 10C at Chicago O’Hare International Airport (ORD), Chicago, Illinois, however, the flight crew inadvertently landed on runway 10L. While on descent and upon initial check-in with the ORD approach controller, the flight crew was instructed to expect runway 10C. They were subsequently cleared for the instrument landing system (ILS) to runway 10C. The flight crew acknowledged and correctly read back the approach clearance. The flight crew stated that the captain, who was the pilot monitoring, briefed the approach, programmed the flight management computer (FMC) with the ILS approach to runway 10C to back up the planned visual approach. However, they were not receiving the ILS identifier. The captain attempted to troubleshoot why the localizer frequency would not autotune by reloading the approach in the FMC and manually tuning the frequency. Unable to resolve the issue they elected to proceed visually. The captain contacted the air traffic control tower (ATCT) controller stating they were on the visual approach to runway 10C, and the airplane was cleared to land on runway 10C. However, the airplane was aligned with and landed on runway 10L. The flight crew’s decision to continue the approach without the correct ILS frequency was likely affected by their task saturation and planned continuation bias, and their inability to perceive and efficiently integrate available information. Planned continuation bias is an unconscious cognitive phenomenon to continue with the original plan in spite of changing conditions. Once a plan is made and committed to, it becomes increasingly difficult for stimuli or changing conditions to be recognized as necessitating a change to the plan. In addition, as workload increases conditions that may appear obvious to individuals external to the situation are difficult for people caught up in the plan to recognize. Recorded data from the flight data recorder revealed that while flying a heading to intercept the ILS 10C, the localizer frequency in the Nav 1 radio was correctly tuned to 108.95 MHz, the frequency for the ILS 10C localizer, for four seconds. Subsequently, the Nav 1 radio was changed to 108.4 MHz and Nav 2 radio was changed to 113.0 MHz for the remainder of the flight. Although the correct ILS frequency (108.95 MHz) was briefly tuned in the Nav 1 radio, it was subsequently changed to an incorrect frequency (108.4 MHz), and Nav 2 was tuned to a non-ILS frequency (113.0 MHz), preventing the crew from confirming alignment with runway 10C.
The FAA mandatory occurrence report (MOR) revealed that the ATCT controller noticed the runway alignment error and coordinated with the runway 10L controller to allow ENY3936 to land on the incorrect runway as no traffic conflicts were noted. The air traffic control (ATC) services provided by the controller were deficient and contrary to FAA directives. Specifically, the controller failed to notify ENY3936 of their alignment error and did not issue control instructions to prevent the wrong surface landing. Had the controller notified the flight crew of the alignment error or provided control instructions it is likely that the wrong surface landing would have been prevented.
Probable cause
The flight crew’s misidentification of the intended landing runway, which resulted in an approach to and landing on the wrong runway due to their planned continuation bias. Contributing to the incident was the flight crew’s decision to continue the approach without the correct ILS frequency in the FMS. Also contributing was air traffic control’s failure to notify the flight crew that the were lined up with the incorrect runway contrary to FAA directives.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA24LA318
- Event ID
- 20240927195210
- Case number
- DCA24LA318
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas, damage. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 48fb3d368486077ee2c503a2b0d39e2753a24bd7d84a9609f0e10fde3e2049e8; retrieved 2026-09-16T19:19:25.437Z.