GAA18CA218 · Piper PA 28-161
Wrong Bros Aviator Training School Piper PA 28-161 · Accident: loss of control on ground during landing
From Mobile Regional Airport (MOB) to Roscoe Field (82J)
Event
- NTSB case
- GAA18CA218
- 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
Piper PA 28-161
- Aircraft type
- Piper PA-28
- 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
- N8115Y
- Onboard fatalities
- Unknown
- Route
- From Mobile Regional Airport (MOB), Mobile, ALTo Roscoe Field (82J), Pensacola, FL
- Aircraft age
- About 39 years (built 1979)
- 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
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Task environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he landed with a left crosswind with about the final third of the 3,200-ft-long runway remaining. He reported that his ground speed was too fast, and after his initial brake application, he increased brake pressure and his right shoe became "stuck between the right pedal and the toe brake." The airplane veered to the right and exited the right side of the runway, striking a runway light before it collided with a creek where it came to rest.
The airplane sustained substantial damage to the engine mount.
According to the METAR located 3 nautical miles from the accident site, about the time of the accident, the wind was from 310° at 12 knots, gusting to 19 knots. The pilot landed on runway 36.
The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s loss of directional control and long landing in gusting wind conditions due to his shoe getting stuck on the brakes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA218
- Event ID
- 20180416X32016
- Case number
- GAA18CA218
- 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: 5254a6bbb8f5f834ec5193b609507882850f8b57a8fb32345ca5c20b9e5fa297; retrieved 2026-09-16T06:50:41.742Z.