BFO92LA126 · Cessna 172E
Cessna 172E · Accident: in flight encounter with weather en route
From N99 · West Chester, PA to Ocean City Municipal Airport (26N)
Event
- NTSB case
- BFO92LA126
- 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
- 1 · 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
- Instrument Meteorological Cond
Cessna 172E
- 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
- N3847S
- Operator
- David L. Erb · private individual
- Onboard fatalities
- Unknown
- Route
- From N99 · West Chester, PATo Ocean City Municipal Airport (26N), Ocean City, NJ
- 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
- In flight encounter with weather
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Spatial disorientation
- Pilot in command › VFR flight into imc, inadvertent
Approximate · Estimated position: the centre of Tuckahoe, NJ, the place the record names. Not the accident site.
NTSB narrative
THE PILOT RECEIVED A WEATHER BRIEFING AT 1630 EST FOR THE FLIGHT. AT THE TIME, HE INDICATED THAT HE WOULD DEPART AT 1900 EST WITH AN EN ROUTE TIME OF 45 MINUTES. HE INDICATED TO A FAMILY MEMBER THAT HE WOULD ARRIVE AT THE DESTINATION BETWEEN 1900 AND 1930 EST. THE PILOT DEPARTED AT AN UNDETERMINED TIME. THE AIRPLANE WAS REPORTED OVERDUE AND SEARCH AUTHORITIES LOCATED THE AIRPLANE TWO DAYS LATER. THE AIRPLANE CRASHED IN A SWAMP AREA, ABOUT 8 MILES WEST OF THE DESTINATION AIRPORT. THE AIRPLANE STRUCK THE GROUND IN A STEEP RIGHT BANK ATTITUDE. THE WRECKAGE WAS STREWN A DISTANCE OF ABOUT 300 FEET. THE WEATHER IN THE AREA AT 2000 EST WAS REPORTED AS 200 FEET OVERCAST AND THE VISIBILITY WAS 0.50 MILES IN FOG. EXAMINATION OF THE AIRPLANE DID NOT DISCLOSE EVIDENCE OF A MECHANICAL MALFUNCTION. THE ACCIDENT WAS PRESUMED TO HAVE OCCURRED AT ABOUT 1945.
Probable cause
VFR FLIGHT BY THE PILOT INTO INSTRUMENT METEOROLOGICAL CONDITIONS (IMC), AND HIS FAILURE TO MAINTAIN CONTROL OF THE AIRCRAFT DUE TO SPATIAL DISORIENTATION. FACTORS RELATED TO THE ACCIDENT WERE: THE LIGHT CONDITIONS AT DUSK (OR DARKNESS), AND THE PILOT'S LACK OF INSTRUMENT EXPERIENCE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO92LA126
- Event ID
- 20001211X15615
- Case number
- BFO92LA126
- 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: 74fc55f3e846802c9c98b3f2b656f1c1df033a32f8722fb182827f3666ba589c; retrieved 2026-09-21T00:58:07.747Z.