BFO95LA047 · Ercoupe (Eng & Research Corp.) 415-C
Ercoupe (Eng & Research Corp.) 415-C · Accident: hard landing
From Millville Municipal Airport (MIV) to Bucks Airport (00N)
Event
- NTSB case
- BFO95LA047
- 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
Ercoupe (Eng & Research Corp.) 415-C
- Aircraft type
- Ercoupe (eng Research 415
- 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
- N99248
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Millville Municipal Airport (MIV), MILLVILLE MUNI, NJTo Bucks Airport (00N)
- 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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 › Recovery from bounced landing, inadequate
Approximate · Estimated position: the centre of Bridgeton, NJ, the place the record names. Not the accident site.
NTSB narrative
THE PILOT STATED THAT WHILE LANDING AT ON AN UNCONTROLLED GRASS STRIP, THE AIRPLANE LANDED HARD, AND BOUNCED TWICE. THE NOSE GEAR COLLAPSED AND THE AIRPLANE CAME TO A STOP, NOSED DOWN. THE PILOT REPORTED THAT DURING THE INITIAL TOUCHDOWN, HE FELT THE AIRPLANE 'ACCELERATE.' THE PILOT REPORTED THAT HE OVERFLEW THE AIRPORT TO CHECK THE WIND SOCK PRIOR TO LANDING AND IT WAS INDICATING CALM WIND. HE STATED THAT AFTER THE ACCIDENT, THE WIND SOCK WAS STANDING 'STRAIGHT OUT.' HE STATED THAT THE WIND DIRECTION WOULD HAVE GIVEN THE AIRPLANE A TAILWIND DURING THE ACCIDENT LANDING. THE PILOT REPORTED THAT THERE WERE NO AIRPLANE MECHANICAL MALFUNCTIONS PRIOR TO THE ACCIDENT.
Probable cause
the student pilot's inadequate recovery from a bounced landing. A factor in the accident was the suddenly changing wind condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO95LA047
- Event ID
- 20001207X03087
- Case number
- BFO95LA047
- 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: 1ca2a41ae497452d60e2b58a3a629cd2e21ccc5df8c7c2cc46ae9bf508dc0ce9; retrieved 2026-09-23T00:06:23.775Z.