GAA16CA193 · Silvaire LUSCOMBE 8A UNDESIGNAT
Silvaire LUSCOMBE 8A UNDESIGNAT · Accident: loss of control on ground during landing
From Anacortes Airport (74S) to Skagit Regional Airport (BVS)
Event
- NTSB case
- GAA16CA193
- 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
Silvaire LUSCOMBE 8A UNDESIGNAT
- Aircraft type
- Silvaire 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
- N28437
- Operator
- Lyle E. Mooney and Steve McClean
- Onboard fatalities
- Unknown
- Route
- From Anacortes Airport (74S), Anacortes, WATo Skagit Regional Airport (BVS), Burlington, WA
- Aircraft age
- About 76 years (built 1940)
- 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 oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot of the tailwheel-equipped airplane, he was practicing stop and go landings on an asphalt runway. He reported that during the third landing, he continued his landing roll to turn off the runway. He reported that he applied the brakes in order to slow down, but inadvertently applied too much pressure to both heel brakes. He recalled that due to the excessive braking the airplane veered right, and then veered left and the airplane subsequently exited the runway to the left and ground looped. Substantial damage was sustained to the right wing.
The pilot reported that there were no mechanical failures or anomalies with the airplane prior to or during the flight that would have prevented normal flight operation.
Probable cause
The pilot's excessive application of the brakes during the landing roll, resulting in a loss of directional control, runway excursion, and ground loop.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA193
- Event ID
- 20160419X22520
- Case number
- GAA16CA193
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-04-19.
- API snapshot SHA-256: 94976ad7da72fbce25b2269d060d8420b73adde2dde4a322ebc0ea413fa0a259; retrieved 2026-09-16T03:18:24.518Z.