WPR13LA063 · Aerotek PITTS S-1T
Aerotek PITTS S-1T · Accident: flight control system malfunction/failure during landing
From Billings Logan International Airport (BIL) to Billings Logan International Airport (BIL)
Event
- NTSB case
- WPR13LA063
- 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
Aerotek PITTS S-1T
- Aircraft type
- Aerotek PITTS S-1T
- 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
- N49309
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Billings Logan International Airport (BIL), Billings, MTTo Billings Logan International Airport (BIL), Billings, MT
- 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
- 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
- Flight control system malfunction/failure
- 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
- Aircraft › Aircraft structures
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After completing a personal flight, the pilot was returning to his home airport. He stated that on the first landing attempt, he was not able to maintain directional control of the airplane during the landing roll, and he aborted the landing. On the second landing attempt, he again was not able to maintain directional control and subsequently realized that there was not enough remaining runway for him to successfully abort the landing. The airplane departed the runway surface and nosed over, coming to rest inverted. Postaccident examination of the airplane revealed that the weld that attached the tailwheel tube to the fuselage had separated. This would have allowed for the tailwheel assembly to freely move left and right without corresponding rudder input, and thus the pilot would not be able to maintain directional control during the landing roll.
Probable cause
The pilot’s inability to maintain directional control during the landing roll because of the failure of the tailwheel support bracket.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13LA063
- Event ID
- 20121206X82018
- Case number
- WPR13LA063
- 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: 344fb23eb1bc9ebd9bccd514f4a30138572314ed0bdd4c3380e4e39289e542e4; retrieved 2026-09-15T20:32:22.845Z.