FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA26LA102 · Cessna 172 S

28 Jan 2026 · New Castle, DE, United States

Infinity Flight Group Cessna 172 S · Accident: wrong surface or wrong airport during landing

From Lehigh Valley International Airport (ABE) to an unrecorded destination

Report a problem

Event

NTSB case
ERA26LA102
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
Accident
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
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
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
General aviation
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

Cessna 172 S

Aircraft type
Cessna 172
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
N969FG
Onboard fatalities
Unknown
Route
From Lehigh Valley International Airport (ABE), Allentown, PATo not recorded
Aircraft age
About 20 years (built 2006)
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 91: General Aviation
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
Substantial

Cause areas

  • Environmental issues › Operating environment
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilots were performing a visual flight rules, cross-country flight at night. The pilots coordinated with air traffic control to perform an instrument approach to the destination airport’s runway 19 that would terminate in a circle to land maneuver to the opposite direction runway 1. The airport was equipped with three runways, two of which had been closed with an accompanying NOTAM issued due to snow and ice that was covering them. Both pilots were aware of the runway closures prior to the flight. During the subsequent right circling maneuver, the left seat (flying) pilot inadvertently aligned the airplane and began a landing approach to runway 32, whose runway edge lights were illuminated despite the runway being closed. The airplane was high on the final approach, so the pilot transitioned into a forward slip. The pilot further described being task saturated while she tried to focus on maintaining airspeed and alignment with the runway using external visual cues and did not recognize that the airplane was approaching the wrong runway. The right seat pilot described that during the left seat pilot’s turn to final approach, he had been looking inside at an electronic device for indications of nearby traffic, and when he looked out, he recalled seeing that the airplane was approaching a runway surrounded by bright lights, including an approach lighting system. Neither pilot recognized the snow-covered runway surface until after the airplane had touched down. During the landing, the airplane’s wings and propeller contacted the ground, resulting in substantial damage to the right wing and fuselage. The manager of the airport’s air traffic control tower stated that all the runway’s lights, including those surrounding the closed runway, had been illuminated at the request of airport operations personnel in order to help melt snow and ice around the lights. The airport’s operations manager stated that the airport had requested that air traffic control tower personnel leave the runway 1/19 runway edge and taxiway lights on, but did not request that the closed runways’ lights be left on. Neither the air traffic control tower manager nor the airport operations manager was able to provide documentation of any lighting requests that had been made. According to FAA order JO 7110.65BB Air Traffic Control, “Do not turn on the runway edge lights when a NOTAM closing the runway is in effect.” Additionally, the airport operations manager reported no lighted “X” markings had been placed on the closed runways, as those markings were typically only placed during temporary closures due to construction. Had the pilots verified the airplane’s heading during the final approach and recognized that it was more than 50 degrees different than that of the intended landing runway, it is likely that the accident could have been avoided. It is also likely that had the closed runway’s lights not been illuminated, consistent with FAA guidance to air traffic controllers, the pilots would not have misidentified and attempted to land on the closed runway.

Probable cause

The pilots’ failure to properly identify the assigned runway during the landing approach, which resulted in the airplane landing on a closed, snow-covered runway. Contributing was the illumination of the closed runway’s edge lighting.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA26LA102
Event ID
20260202202369
Case number
ERA26LA102
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: local date, investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2026-01-29.
  • API snapshot SHA-256: 4cdd2f67dfbd0b8c51c58b18c764a9406bdf54e622784605a339d8cfc4cc585c; retrieved 2026-09-16T20:42:33.952Z.