NYC07CA019 · Cessna 172M
Norfolk Aviation Cessna 172M · Accident: airframe, component or system failure en route
From Emporia Greensville Regional Airport (EMV) to Astra Ksetra Airport (AKQ)
Event
- NTSB case
- NYC07CA019
- 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
- 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
- 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 172M
- 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
- N20931
- Operator
- Norfolk Aviation
- Onboard fatalities
- Unknown
- Route
- From Emporia Greensville Regional Airport (EMV), Emporia, VATo Astra Ksetra Airport (AKQ)
- Aircraft age
- Not recorded
- 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
- En route · cruise
- First occurrenceThe 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
- Airframe, component or system failure
- 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
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While on a solo cross country flight in a Cessna 172M, the student pilot elected to divert instead of continuing with his planned flight after the airplane's radios began to operate intermittently and the electrical system failed. During the landing at the diversionary airport, the winds were gusting at 18 to 25 knots, though the winds had been originally forecasted to be favorable for his route of flight. During the landing the airplane lost "lift," touched down on the nose landing gear, and porpoised about three times before the student pilot was able to regain control. A post accident examination of the airplane revealed that it had incurred substantial damage. No anomalies with the electrical system were discovered.
Probable cause
The student pilot's failure to maintain control during the landing. A factor to the accident was the wind gusts.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC07CA019
- Event ID
- 20061204X01726
- Case number
- NYC07CA019
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 2ff6648e35cdf1f8ed87782732a7ae90408bba3bfb26d7a8feaabe4e03f5cad3; retrieved 2026-09-22T04:16:36.976Z.