FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA224 · Luscombe 8 F

20 Apr 2019 · Bremen, AL, United States

Luscombe 8 F · Accident: nose over/nose down during takeoff

From Bremen, AL (private airstrip) to Bremen, AL (private airstrip)

Report a problem

Event

NTSB case
GAA19CA224
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

Luscombe 8 F

Aircraft type
Luscombe 8
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
N1866B
Operator
Ronald J Morrison · private individual
Onboard fatalities
Unknown
Route
From Bremen, AL (private airstrip)To Bremen, AL (private airstrip)
Aircraft age
About 71 years (built 1948)
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
Takeoff · rejected takeoff
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

  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot of the tailwheel-equipped airplane reported that, during takeoff from a 2,400-ft-long private, grass airstrip, he was concerned the airplane would not clear the wires at the end of the runway, so he aborted the takeoff. The airplane overran the departure end of the runway, crossed a road, and went through a barbed wire fence. Subsequently, the airplane come to rest inverted.

The airplane sustained substantial damage to the left wing and wing lift strut.

The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

About the time of the accident, the pilot estimated that the wind was from 290° at 8 knots. The pilot was departing from runway 18.

Probable cause

The pilot's delayed decision to abort the takeoff, which resulted in a runway overrun, impact with a fence, and a nose-over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA224
Event ID
20190420X85338
Case number
GAA19CA224
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: 023501758ada892b7f7dc1c9df5f08cec11d64a9dfe96b15db2f19cce5d6ace5; retrieved 2026-09-16T08:47:21.389Z.