ERA11CA199 · Luscombe 8E
Luscombe 8E · Accident: loss of control on ground during landing
From Richmond Airport (08R) to Taunton Municipal King Field (TAN)
Event
- NTSB case
- ERA11CA199
- 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 8E
- 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
- N2790K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Richmond Airport (08R), West Kingston, RITo Taunton Municipal King Field (TAN), Taunton, MA
- 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
- 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 systems
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that the purpose of the flight was to prepare for a biennial flight review. The approach and landing were uneventful; however, on the landing roll, at taxi speed, a strong crosswind gust, which exceeded rudder authority, causing the airplane to ground loop. The pilot applied the brakes which resulted in the airplane nosing over incurring substantial damage to the fuselage, wings, and empennage sections. The pilot stated that the wind was variable from 030 to 300 degrees gusting from 12 knots to 22 knots, and there were no mechanical failures or malfunctions of the airplane or any of its systems prior to the accident.
Probable cause
The pilot's inadvertent application of the brakes during recovery from a ground loop which resulted in a nose over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA199
- Event ID
- 20110320X83852
- Case number
- ERA11CA199
- 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: e3c5e6ce0b98e692da49e2040ee7d1e6d5b08ac560b1a3f9cdecffd5e6b80802; retrieved 2026-09-15T15:56:26.750Z.