FTW98LA414 · Pitts S-2B
Pitts S-2B · Accident: loss of control in flight during landing
From F39 to an unrecorded destination
Event
- NTSB case
- FTW98LA414
- 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
Pitts S-2B
- Aircraft type
- Pitts S-2
- 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
- N52TW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From F39To 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 in flight
- 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
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the tail wheel equipped airplane lost directional control while landing on runway 17L due to a crosswind condition. The private pilot stated that just prior to the wheels contacting the runway a gust of wind 'from 090 degrees' pushed the airplane to the right of the runway centerline. The airplane contacted the runway to the right of the runway centerline and the pilot began to use left rudder and braking to maintain directional control of the airplane. Subsequently, the tail of the airplane began to swing around to the right and the right main landing gear collapsed. The airplane slid approximately 15 feet and came to rest upright on the runway. The pilot estimates that at the time of the accident the winds were from 090 degrees at 10 to 12 knots and gusting to 15 knots.
Probable cause
The failure of the pilot in command to maintain directional control of the airplane during the landing flare. A factor was the gusty, crosswind condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA414
- Event ID
- 20001211X10868
- Case number
- FTW98LA414
- 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: faaa15e293645689c673bf9a6f243e06b1eaf8f9bb9c7dce03c681f71b9af911; retrieved 2026-09-22T16:57:12.329Z.