BFO94LA115 · Taylorcraft F19
Taylorcraft F19 · Accident: hard landing
From OB2 · Brewer, ME to OB2 · ME
Event
- NTSB case
- BFO94LA115
- 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
- Instrument Meteorological Cond
Taylorcraft F19
- Aircraft type
- Taylorcraft F19
- 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
- N2000U
- Operator
- Rodney L Hanscom · private individual
- Onboard fatalities
- Unknown
- Route
- From OB2 · Brewer, METo OB2 · ME
- 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
- 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 › Airspeed, misjudged
- Pilot in command › Altitude, misjudged
Approximate · Estimated position: the centre of Orrington, ME, the place the record names. Not the accident site.
NTSB narrative
ACCORDING TO THE FAA, THIS WAS THE PILOT'S FIRST TIME LANDING ON THIS SOFT, SHORT, UPSLOPE FIELD. THE PILOT STATED THAT THE WINDS WERE CALM, AND FINAL APPROACH WAS FAIRLY STEEP. HE STATED THAT HE FLARED AT APPROXIMATELY 45 MPH, BUT FAILED TO ARREST THE HIGH RATE OF DESCENT. ACCORDING TO THE PILOT, THE AIRPLANE'S RIGHT MAIN GEAR SANK INTO THE SOFT FIELD AND THE AIRCRAFT NOSED DOWN FOR A MOMENT THEN CAME TO REST IN AN UPRIGHT POSITION. THE PILOT REPORTED THAT THERE WAS NO MECHANICAL MALFUNCTION, AND THE ACCIDENT COULD HAVE BEEN PREVENTED IF HE HAD MORE AIRSPEED AND APPROACHED THE UPSLOPING FIELD AT A SHALLOWER ANGLE.
Probable cause
THE PILOT MISJUDGED HIS ALTITUDE AND AIRSPEED WHICH RESULTED IN A HARD LANDING. RELATED FACTORS WERE THE SOFT, AND UPSLOPE FIELD.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO94LA115
- Event ID
- 20001206X01472
- Case number
- BFO94LA115
- 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: 32b230304b4565b6be5588cef435001d9c46397f43f1d54a9bda70de00adc983; retrieved 2026-09-23T01:00:20.524Z.