ATL98LA085 · Stroud SKY BOLT
Stroud SKY BOLT · Accident: loss of control on ground/water during landing
From Twin Lakes Airport (8A7) to an unrecorded destination
Event
- NTSB case
- ATL98LA085
- 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
- 0
- 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
Stroud SKY BOLT
- Aircraft type
- Stroud SKY BOLT
- 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
- N2951S
- Operator
- Joe e Mcglothlin · private individual
- Onboard fatalities
- Unknown
- Route
- From Twin Lakes Airport (8A7)To not recorded
- 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 · flare/touchdown
- First occurrenceThe 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/water
- 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
- Flight control, rudder › Movement restricted
- Passenger › Aircraft control, restricted
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the FAA, during landing on runway 09, the aircraft veered off the right side of the runway and nosed over. The inspector found a 300 foot skid mark made by the left main landing gear, and a 150 foot skid mark, made by the right main landing gear. The aircraft received substantial damage to the propeller, rudder, and left wing. On the landing roll, the pilot applied rudder to get the airplane onto the runway centerline, the foot of the occupant in the front seat was pressed onto the opposite brake peddle causing the airplane to react slowly. The harder the pilot applied the rudder, the harder the opposite brake was actuated. As the airplane started to depart the runway, the pilot said he applied left brake. Inertia caused the airplane to nose over. The pilot shut the airplane down and he and the passenger egressed from the inverted airplane.
Probable cause
The pilot's loss of directional control during landing roll when the front seat occupant inadvertently got his foot 'jammed' between the strut bungee and the rudder/brake peddle. A factor was the inadequate design of the rudder/brake peddle system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL98LA085
- Event ID
- 20001211X10232
- Case number
- ATL98LA085
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 67a9ee5dc86ab4979af3846f0503cd3d45603b3a0d2393fff533b4ad9d08131d; retrieved 2026-09-22T17:37:47.444Z.