FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19LA199 · Taylorcraft BC12 D

17 Jun 2019 · Readington, NJ, United States

Taylorcraft BC12 D · Accident: nose over/nose down during landing

From Solberg/Hunterdon Airport (N51) to Solberg/Hunterdon Airport (N51)

Report a problem

Event

NTSB case
ERA19LA199
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
Unknown
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

Taylorcraft BC12 D

Aircraft type
Taylorcraft BC12
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
N43766
Operator
Unknown
Onboard fatalities
Unknown
Route
From Solberg/Hunterdon Airport (N51), Readington, NJTo Solberg/Hunterdon Airport (N51), Readington, NJ
Aircraft age
About 73 years (built 1946)
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
Defining eventThe 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
Nose over/nose down
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot performed two landings on a turf runway and returned for a third approach. The pilot aligned the airplane parallel to the intended runway, about 80 feet to the left of the mowed runway surface. The airplane touched down in dense grass about 3-4 feet tall and travelled about 80 feet before it nosed over and came to rest inverted. The pilot insisted that the brakes had "locked;" however, examination of the airplane revealed that with the brakes fully applied there was little to no braking action and that the airplane rolled with little to no resistance. The accident is consistent with the airplane nosing over due to the landing in tall grass.

Probable cause

The pilot's failure to land on the mowed turf runway, which resulted in the airplane landing in tall grass and subsequently nosing over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19LA199
Event ID
20190620X40504
Case number
ERA19LA199
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 65c3c0c409f17c18b957623613a6c677cf26d2b392a40f072e853d6e47b82ecf; retrieved 2026-09-16T09:18:21.666Z.