BFO85FA042 · Cessna 175
Cessna 175 · Accident: total loss of engine power (non-mechanical) en route
From Smith Mountain Lake Airport (W91) to Cambridge Dorchester Airport (CGE)
Event
- NTSB case
- BFO85FA042
- 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 175
- Aircraft type
- Cessna 175
- 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
- N7027E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Smith Mountain Lake Airport (W91), MONETA, VATo Cambridge Dorchester Airport (CGE), Cambridge, MD
- 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Preflight planning/preparation, inadequate
- Pilot in command › Proper glidepath, not attained
- Pilot in command › Proper touchdown point, exceeded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT FLEW 2:15 FROM CAMBRIDGE, MD, TO SMITH MOUNTAIN LAKE, VA, EARLIER ON THE DAY OF THE ACCIDENT AND WAS 2 HRS INTO THE RETURN FLT WHEN AT 5500 FT OVER PRINCE FREDERICK, MD, THE ENG LOST PWR DUE TO FUEL EXHAUSTION, ACCORDING TO THE PASSENGER. THE APCH TO THE PRIVATE STRIP SELECTED FOR THE FORCED LANDING WAS TOO HIGH, THE PLT STATED, AND TOUCHDOWN WAS BETWEEN HALF AND TWO-THIRDS DOWN THE 1850 FT RWY. THE ACFT COULD NOT BE STOPPED ON THE REMAINING RWY AND AN ATTEMPT TO TURN RIGHT AND AVOID TREES WAS UNSUCCESSFUL. THE ACFT HAD RECEIVED MAINTENANCE ON THE FUEL GAGES ON 4/29/85. THE LEFT FUEL GAGE SENDER WAS NOT FUNCTIONING PROPERLY AT THAT TIME. ADDITIONALLY, THE PASSENGER, A STUDENT PLT STATED THAT THE FUEL GAGES WERE FUNCTIONING AT THE TIME OF THE ACCIDENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record BFO85FA042
- Event ID
- 20001214X36376
- Case number
- BFO85FA042
- 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: 6574bcbc119fe9e1d9e7f5d7dccbdaf308d067371e115086181c579976143415; retrieved 2026-09-22T01:51:25.564Z.