FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI82IA331 · Swearingen SA-226TC

1 Sept 1982 · Appleton, WI, United States

Air Wisconsin Swearingen SA-226TC · Incident: airframe, component or system failure during initial climb

From Appleton International Airport (ATW) to Appleton International Airport (ATW)

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
CHI82IA331
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
Incident
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

Swearingen SA-226TC

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
N261S
Onboard fatalities
Unknown
Route
From Appleton International Airport (ATW), Appleton, WITo Appleton International Airport (ATW), Appleton, WI
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
Initial climb
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
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Company maintenance personnel › Maintenance, adjustment, improper
  • Door, landing gear › Movement restricted
  • Landing gear, main gear › Jammed
  • Landing gear, normal retraction/extension assembly › Jammed

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE RIGHT MAIN GEAR "IN TRANSIT" LIGHT REMAINED ON AFTER GEAR RETRACTION ON A TRAINING FLIGHT. VARIOUS METHODS OF REMEDIAL ACTION DID NOT CURE THE PROBLEM. A LANDING ON RUNWAY 21 WAS EXECUTED WITH THE NOSE AND LEFT MAIN GEAR IN THE DOWN POSITION. THE RIGHT GEAR REMAINED IN TRANSIT. DIRECTIONAL CONTROL WAS MAINTAINED NEARLY THROUGHOUT THE LANDING ROLL. PRIOR TO THIS FLIGHT, COMPANY MAINTENANCE PERSONNEL HAD INSPECTED THE GEAR IN COMPLIANCE WITH A TELEGRAPHIC MESSAGE FROM THE MANUFACTURER. THE INSPECTION WAS INITIATED BY ONE MAINTENANCE SHIFT AND COMPLETED BY ANOTHER. INSUFFICIENT INFORMATION WAS PASSED BETWEEN THE SHIFTS TO ENSURE THAT GEAR DOOR WAS PROPERLY RE-RIGGED. DURING GEAR EXTENSION, THE DOOR JAMMED PREVENTING COMPLETE EXTENSION OF THE GEAR.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record CHI82IA331
Event ID
20020917X04422
Case number
CHI82IA331
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1982-09-02.
  • API snapshot SHA-256: 32b70c392ca0acd7c10fd0c2ae180988a520df69d393e9c8a55cb7559d2d71fc; retrieved 2026-09-24T01:07:46.227Z.