BFO94LA142 · Piper J3C-65
Piper J3C-65 · Accident: overrun during landing
From OH (private airstrip) to an unrecorded destination
Event
- NTSB case
- BFO94LA142
- 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
Piper J3C-65
- Aircraft type
- Piper J3
- 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
- N92483
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From OH (private airstrip)To not recorded
- 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 · landing roll
- 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
- Overrun
- 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 › Airspeed, misjudged
- Pilot in command › Altitude, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT HE WAS PRACTICING TAKEOFFS AND LANDINGS AT THE PRIVATE GRASS STRIP. HE REPORTED THAT A THUNDERSTORM PASSED THROUGH THE AREA EARLIER, AND THAT THE 2000 FOOT LONG, GRASS STRIP WAS WET. HE STATED THAT HE HAD COMPLETED FIVE NORMAL LANDINGS SUCCESSFULLY EARLIER THAT DAY. ACCORDING TO THE PILOT, THE TAKEOFF WAS NORMAL, AND ON FINAL APPROACH TO RUNWAY 7, THE AIRPLANE WAS HIGHER THAN NORMAL. THE PILOT STATED THAT THE AIRPLANE FLOATED A SHORT DISTANCE BEFORE IT TOUCHED DOWN. HE STATED THAT UPON TOUCHDOWN HE APPLIED THE BRAKES, BUT DUE TO THE WET GRASS HE WAS UNABLE TO STOP IN TIME TO AVOID STRIKING THE FENCE AT THE DEPARTURE END OF THE RUNWAY. AN FAA AVIATION SAFETY INSPECTOR EXAMINED THE AIRPLANE AFTER THE ACCIDENT AND REPORTED THAT THE BRAKES WERE OPERATIONAL. THE PILOT ALSO REPORTED THAT THERE WAS NO MECHANICAL MALFUNCTION.
Probable cause
THE PILOT MISJUDGED HIS ALTITUDE AND AIRSPEED DURING LANDING RESULTING IN AN OVERRUN AND COLLISION WITH A FENCE. A RELATED FACTOR WAS THE WET RUNWAY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO94LA142
- Event ID
- 20001206X01966
- Case number
- BFO94LA142
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1994-08-21.
- API snapshot SHA-256: 87904c7653ebc3e83652aaf0a42245ea7b4601160706d067bd29fba7944aae2e; retrieved 2026-09-23T00:47:16.593Z.