GAA16CA280 · Staudacher Aircraft Inc S 300
Staudacher Aircraft Inc S 300 · Accident: hard landing
From Chicago Executive Airport (PWK) to Chicago Executive Airport (PWK)
Event
- NTSB case
- GAA16CA280
- 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
Staudacher Aircraft Inc S 300
- Aircraft type
- Staudacher S-300
- 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
- N126RG
- Operator
- Petersen, Alfred C. · private individual
- Onboard fatalities
- Unknown
- Route
- From Chicago Executive Airport (PWK), Prospect Heights, ILTo Chicago Executive Airport (PWK), Prospect Heights, IL
- Aircraft age
- About 18 years (built 1998)
- 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
- 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
- Hard landing
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot of the tailwheel-equipped airplane reported that he landed hard and bounced. The pilot further reported that after the bounce, he knew that the left main landing gear had collapsed, and he held the left wing off of the runway until the airplane slowed and the wing stopped producing lift. Subsequently, the airplane veered off the runway to the left and collided with runway signs, which resulted in substantial damage to the horizontal stabilizer.
The pilot reported that the "½ inch fine thread bolt" on the left main landing gear failed during the bounced landing.
Probable cause
The pilot's incorrect pitch control during the landing, which resulted in a hard bounced landing, and subsequent left main landing gear collapse, a runway excursion, and a collision with a runway sign.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA280
- Event ID
- 20160606X62610
- Case number
- GAA16CA280
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-06-03.
- API snapshot SHA-256: b25a1d0b56f12a60a5d4256d2d7489f093ce19d5089df4038d283dda33d7c737; retrieved 2026-09-16T03:28:04.430Z.