FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA83LA102 · Cessna TRI82

20 May 1983 · Idaho Falls, ID, United States

Cessna TRI82 · Accident: total loss of engine power (mechanical failure) during initial climb

From Idaho Falls Regional Airport (IDA) to AFT · Afton, WY

Report a problem

Event

NTSB case
SEA83LA102
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

Cessna TRI82

Aircraft type
Cessna TRI82
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
N757SP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Idaho Falls Regional Airport (IDA), Idaho Falls, IDTo AFT · Afton, WY
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
Total loss of engine power (mechanical failure)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Ignition system, magneto › Loose
  • Other maintenance personnel › Maintenance, compliance with ad, improper

Approximate · Estimated position: the centre of Idaho Falls, ID, the place the record names. Not the accident site.

NTSB narrative

DURING TAKEOFF, THE ENGINE LOST POWER AFTER THE PLT STARTED TO MAKE A TURN AT APRX 500 FT AGL. AN EMERGENCY LANDING WAS MADE IN A PLOWED FIELD WITH THE GEAR & FLAPS RETRACTED. AFTER TOUCHDOWN, THE ACFT SLID APRX 100 YARDS, THEN STOPPED IN A CANAL. AN INVESTIGATION REVEALED THAT THE ACFT HAD JUST RECEIVED MAINTENANCE ON THE MAGNETOS FOR COMPLIANCE OF AN AD WHICH REQUIRE REPLACEMENT OF A GEAR. AN ENGINE TEARDOWN REVEALED THAT A RETAINING SCREW FOR THE CAM IN THE MAGNETO WAS LOOSE. REPORTEDLY, THE PASSENGER WAS NOT WEARING A SHOULDER HARNESS & RECEIVED A FRACTURED STERNUM & MULTIPLE BRUISES, ESPECIALLY ABOUT THE HEAD.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record SEA83LA102
Event ID
20001214X43152
Case number
SEA83LA102
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: 7973afd6ea88ba814f319ac788339ae54b4cc8e1fb1dbc43faddd89287e113c9; retrieved 2026-09-21T17:57:00.049Z.