# NTSB ERA26LA102: Cessna 172, N969FG, New Castle, DE, January 29, 2026 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 4 · Limited · Final report - Date: January 28, 2026, 20:44 local (Jan 29, 2026, 01:44 UTC) - Place: New Castle, DE - Coordinates: 39.672654, -75.605241 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.6727&lon=-75.6052&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Wrong surface or wrong airport](https://openairdocs.org/ntsb-events/284) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report May 14, 2026 - Report: Approved by Office Director - Investigation class: Class 4 - Basic report with no Prelim publish - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 202369 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA26LA102 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/202369/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=202369 - Page: https://openairdocs.org/ntsb/ERA26LA102 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Info processing/decision: identification/recognition](https://openairdocs.org/ntsb-findings/02041510): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172S, 10 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md?model=2072439), [All aircraft, 559 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md) - [Runway/land/takeoff/taxi surface: snow/slush/ice covered surface](https://openairdocs.org/ntsb-findings/03023015): Environmental issues › Physical environment · Effect on operation; cases with it: [Cessna 172S, 6 cases](https://openairdocs.org/ntsb-findings/03023015/cases.md?model=2072439), [All aircraft, 219 cases](https://openairdocs.org/ntsb-findings/03023015/cases.md) - [Airport facilities/design: runway lighting](https://openairdocs.org/ntsb-findings/03017015): Environmental issues › Operating environment · Effect on personnel (probable cause); cases with it: [Cessna 172S, 1 case](https://openairdocs.org/ntsb-findings/03017015/cases.md?model=2072439), [All aircraft, 18 cases](https://openairdocs.org/ntsb-findings/03017015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Wrong surface or wrong airport](https://openairdocs.org/ntsb-events/284) (defining event); cases with it: [Cessna 172S, 1 case](https://openairdocs.org/ntsb-events/284/sequence.md?model=2072439), [All aircraft, 56 cases](https://openairdocs.org/ntsb-events/284/sequence.md) - [Landing: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072439), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) ## Analysis 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, thepilots would not have misidentified and attempted to land on the closed runway. ## Aircraft - Registration: [N969FG](https://openairdocs.org/aircraft/N969FG), registered now, S/N 172S10373, built 2006 (OpenAirDocs) - Reported make and model: CESSNA 172 (S) - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S10373 - Year built: 2006 - Airframe hours: 10136.4 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Infinity Flight Group - Registered owner: Mustang Sally Aviation LLC - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: Annual, January 12, 2026, 33 hours before - Departed: ABE, Allentown, PA - Destination: Same as departure - Airport: ILG, New Castle, runway 32, 4,602 × 150 ft, asphalt - Equipment: Electronic multifunction display, Electronic primary flight display, Stall warning system, ADS-B, Auto-pilot, Electronic flight bag or handheld device ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 35; injuries: none; commercial, military; airplane ratings: single-engine land; instrument ratings: helicopter; medical: class 1, without waivers/limitations; last flight review January 21, 2026; seat: left; restraint: 3-point; flight hours: 677 total, 119 in this make and model, 148 as pilot in command, 100 in the last 90 days, 21 in the last 30 days, 3 in the last 24 hours - Pilot; age 40; injuries: none; commercial, military; airplane ratings: single-engine land; instrument ratings: airplane, helicopter; medical: class 1, without waivers/limitations; last flight review October 29, 2025; seat: right; restraint: 3-point; flight hours: 2,709 total, 126 in this make and model, 1,838 as pilot in command, 112 in the last 90 days, 40 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night - Wind: 320° at 4 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 12 °F, dew point 1 °F - Altimeter: 30.11 inHg - Observed at: ILG - METAR: METAR KILG 290151Z AUTO 32004KT 10SM CLR M11/M17 A3011 RMK AO2 SLP196 T11061167 $ ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20260128000939A](https://openairdocs.org/incident/20260128000939A), Jan 28, 2026: Cessna 172S, Wilmington, DE, Substantial damage. The PIC was conducting a circling approach to runway 1. Runway 1 and runway 32 lights were illuminated. The PIC aligned with runway 32 which was reported… ## Docket (14 files) The files NTSB released with the investigation on May 14, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=202369. 24.2 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 4.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20146140&FileExtension=pdf&FileName=6120.1%20completed%20and%20signed_Redacted-Rel.pdf - Airport diagram (ilg) provided by pilot with notes (item 2, PDF, 1 page, 362 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20145957&FileExtension=pdf&FileName=Airport%20Diagram%20-%20Feb%205%202026%20-%2014-30-Rel.pdf - Memorandum for record a�� right seat pilot statement (item 3, PDF, 2 pages, 74 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20154883&FileExtension=pdf&FileName=MOR%20Right%20Seat%20Pilot_Redacted-Rel.pdf - Memorandum for record a�� flight school director of safety statement (item 4, PDF, 1 page, 65 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20154444&FileExtension=pdf&FileName=MOR%20Director%20Of%20Safety_Redacted-Rel.pdf - FAA ATC package ilg (item 5, PDF, 56 pages, 6.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20146490&FileExtension=pdf&FileName=ILG%20ATC%20Package_Redacted-Rel.pdf - Memorandum for record a�� air traffic control tower manager statement (item 6, PDF, 1 page, 64 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20146376&FileExtension=pdf&FileName=MOR%20ATM%20Statement%20(Lighting)-Rel.pdf - Ilg air traffic control tower lighting control pannel (item 7, PDF, 1 page, 7.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20145947&FileExtension=pdf&FileName=ILG%20ATCT%20Lighting%20Control%20Panel-Rel.pdf - FAA order jo 7110.65BB (air traffic control) excerpt (item 8, PDF, 1 page, 86 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20146232&FileExtension=pdf&FileName=JO%207110.65BB%20Runway%20Edge%20Lighting-Rel.pdf - Runway closed NOTAMS (item 9, PDF, 2 pages, 147 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20145656&FileExtension=pdf&FileName=Runway%20Closed%20NOTAMs-Rel.pdf - Memorandum for record a�� airport operations manager (ilg) correspondence (item 10, PDF, 2 pages, 89 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20146386&FileExtension=pdf&FileName=MOR%20Airport%20Ops_Redacted-Rel.pdf - Advisory circular 150-5340-1M (standards for airport markings) excerpt (item 11, PDF, 1 page, 145 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20146158&FileExtension=pdf&FileName=AC%20150-5340-1M%20Excerpt-Rel.pdf - Advisory circular 150-5370-2G (operational safety on airports during construction) (item 12, PDF, 95 pages, 2.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20146396&FileExtension=pdf&FileName=AC%20150-5370-2G-Rel.pdf - Pilot's handbook of aeronautical knowledge (phak)(FAA-H-8083-25C) excerpt (item 13, PDF, 2 pages, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20146500&FileExtension=pdf&FileName=PHAK%20Closed%20Runways-Rel.pdf - Photos and information from flight school (item 14, PDF, 5 pages, 194 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20146242&FileExtension=pdf&FileName=Photos%20and%20Information%20from%20Flight%20School-Rel.pdf From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.