Cessna 172 N969FG
29 January 2026 · New Castle, Delaware, United States · No injuries
Summary
On 29 January 2026 at about 01:44 local time, a Cessna 172 registered N969FG, operated by Infinity Flight Group, was involved in an accident near New Castle, Delaware, United States. 2 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 01:44
- Classification
- Accident
- Location
- New Castle, Delaware, United States
- Nearest airport
- New Castle (ILG)
- Coordinates
- 39.6727, -75.6052
- Aircraft
- Cessna 172
- Registration
- N969FG
- Category
- Airplane
- Year built
- 2006
- Engines
- 1
- Operator
- Infinity Flight Group
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Allentown → Unknown
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Night
- NTSB number
- ERA26LA102
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 0 | 0 | 0 | 2 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Cessna 172 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 11 Apr 2026 | Cessna 172S | Marathon, Florida, United States | Phoenix East Aviation LLC | No injuries | - |
| 9 Jun 2026 | Cessna 172 | Cleburne, Texas, United States | DGJ TEX LLC DBA | No injuries | - |
| 13 Apr 2026 | Cessna 172S | The Rock, Georgia, United States | US Aviation Academy | No injuries | - |
| 11 Jun 2026 | Cessna 172S | Morgan Hill, California, United States | Golf November Aero LLC | No injuries | - |
| 8 Feb 2026 | Cessna 172M | Mangalur, India | M/s Redbird Flying Training Pvt. Ltd. | Minor injuries | - |
| 12 Jun 2026 | Cessna 172 | 6th of October City, Egypt | - | Fatal | 1 |
All 12,209 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 8 Feb 2025 | Vulcanair S P A VULCANAIR V1.0 | Cheswold, Delaware, United States | Delaware State University Aviation Program | Minor injuries | - |
| 9 Sep 2025 | Schweizer G-164B | Dover, Delaware, United States | Air Enterprises LLC | Minor injuries | - |
| 14 Jun 2024 | Van's RV6 | Townsend, Delaware, United States | - | Serious injuries | - |
| 4 Jul 2024 | Bellanca 8GCBC | Frankford, Delaware, United States | Ocean Aerial ADS Inc | Minor injuries | - |
| 25 Aug 2022 | Cessna T210N | Georgetown, Delaware, United States | Bernard A Heckman MD PA | No injuries | - |
| 27 Aug 2020 | Van's RV6 | Milton, Delaware, United States | - | Minor injuries | - |