FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA248 · Luscombe 8 A

19 May 2016 · Blue Bell, PA, United States

Luscombe 8 A · Accident: loss of control on ground during takeoff

From Wings Field (LOM) to Wings Field (LOM)

Report a problem

Event

NTSB case
GAA16CA248
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 A

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
N62925
Operator
Unknown
Onboard fatalities
Unknown
Route
From Wings Field (LOM), Blue Bell, PATo Wings Field (LOM), Blue Bell, PA
Aircraft age
About 70 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
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
Loss of control on ground
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
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During an instructional checkout flight, the pilot of the tailwheel equipped airplane reported that after the tailwheel came up during the takeoff roll, the airplane yawed to the right. The pilot further reported that the flight instructor took over the flight controls, but the airplane continued off of the runway to the right and impacted a ditch.

According to the flight instructor there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

The airplane sustained substantial damage to the left wing.

Probable cause

The pilot's failure to maintain directional control during the takeoff roll and the flight instructor's delayed remedial action, which resulted in runway excursion, and collision with a ditch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA248
Event ID
20160519X65409
Case number
GAA16CA248
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, coordinates. 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: 8c3ad8101b3598e558c704ab9a9936c3b99e15640a54a26928370621bf5ed3b0; retrieved 2026-09-16T03:24:49.378Z.