NYC97LA158 · Cessna 172 RG
Mercury Flight Center Cessna 172 RG · Accident: airframe, component or system failure en route
From Norfolk International Airport (ORF) to Richmond International Airport (RIC)
Event
- NTSB case
- NYC97LA158
- 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 RG
- 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
- N9647B
- Operator
- Mercury Flight Center
- Onboard fatalities
- Unknown
- Route
- From Norfolk International Airport (ORF), Norfolk, VATo Richmond International Airport (RIC), Richmond, VA
- 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 › Wheels up landing, not identified
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was in cruise flight when he discovered that neither the radios nor the fuel gauges were operating. The airplane had flown approximately one hour on full fuel tanks. The pilot chose to make a precautionary landing at an airport 10 miles prior to his destination. The pilot stated that he lowered the landing gear '...and received what I thought was a safe gear indication.' Two witnesses stated they saw the airplane over the runway with the main landing gear out of the wheel wells, but not completely down and locked. Before they could advise the pilot over the radio, the airplane touched down. After touchdown, the main gear collapsed and the airplane departed the left side of the runway. In a written statement, the pilot said, 'During the flight, I didn't notice the low voltage light on the ammeter.' The examination of the airplane included a check of the battery voltage which showed 19.5 volts. This reading immediately dropped to 9 volts when the master switch was turned on. The gear warning horn operated when the throttle was retarded. The low voltage light illuminated, however it was difficult to see without shielding it from the sunlight. The battery was placed on a charger and the engine was started. The ammeter showed a positive charge, indicating the alternator was operating.
Probable cause
The pilot's failure to identify an unsafe landing gear condition. A factor in the accident was the loss of electrical power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC97LA158
- Event ID
- 20001208X08722
- Case number
- NYC97LA158
- 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. 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: 3fcc965238740578701c0b13fca5a3682145c1b4e16363dccc693dcea1058308; retrieved 2026-09-22T18:53:57.963Z.