Iowa Flying Services Swearingen SA-226T accident
Swearingen SA-226T · Accident: in flight collision with terrain/water during landing
From St. Louis Lambert International Airport (STL) to an unrecorded destination
Event
- NTSB case
- CHI92LA038
- 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Swearingen SA-226T
- Aircraft type
- Swearingen SA-226
- 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
- N14TP
- Operator
- Iowa Flying Services
- Onboard fatalities
- Unknown
- Route
- From St. Louis Lambert International Airport (STL), ST LOUIS, MOTo 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 135: Air Taxi & Commuter
- 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
- In flight collision with terrain/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
- Pilot in command › Gear extension, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING THE SECOND LANDING ATTEMPT, THE PILOT FAILED TO LOWER THE LANDING GEAR. THE PILOT EXECUTED A GO-AROUND AFTER THE PROPELLERS CONTACTED THE RUNWAY. THE AIRPLANE THEN RETURNED FOR AN UNEVENTFUL GEAR DOWN LANDING. POST ACCIDENT INSPECTION REVEALED THAT ABOUT ONE THIRD OF EACH BLADE ON THE RIGHT PROPELLER HAD SEPARATED. PIECES OF THE SEPARATED BLADE(S) PUNCTURED A HOLE IN THE PRESSURIZED FUSELAGE.
Probable cause
THE PILOT'S FAILURE TO EXTEND THE LANDING GEAR WHICH RESULTED IN THE PROPELLER BLADES CONTACTING THE RUNWAY DURING THE LANDING. A FACTOR RELATED TO THE ACCIDENT WAS THE PILOT'S FAILURE TO FOLLOW A CHECKLIST DURING THE APPROACH.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI92LA038
- Event ID
- 20001212X18556
- Case number
- CHI92LA038
- 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: 601a35aeceb7a420a01e2f747938ac8e180e5f71162c6ac2dad0fb2e2b245a25; retrieved 2026-09-18T18:50:01.049Z.