FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI98IA035 · Cessna 152

12 Nov 1997 · Blaine, MN, United States

Cessna 152 · Incident: airframe, component or system failure while maneuvering

From Angers Marcé airport (ANE) to an unrecorded destination

Report a problem

Event

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

Cessna 152

Aircraft type
Cessna 152
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
N48863
Operator
Unknown
Onboard fatalities
Unknown
Route
From Angers Marcé airport (ANE)To 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
Maneuvering
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

  • Flt control syst, wing flap control cable/rod › Fatigue
  • Flt control syst, wing flap control cable/rod › Fractured

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

NTSB narrative

The instructor and student were practicing stalls, and on a recovery from a stall the instructor heard a loud 'bang', followed by a roll to the left. After ensuring that the aircraft was under control, the instructor performed a visual inspection of the aircraft, and discovered that the left flap was retracted, while the right flap was still extended. After troubleshooting without success, the instructor had the student fly the aircraft back to the airport. They landed the aircraft without any problems. Post accident examination by the NTSB Materials Laboratory revealed that the flap cable was fatigued and had fractured due to fatigue.

Probable cause

the fracture of the flap cable as a result of fatigue cracking.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI98IA035
Event ID
20001208X09141
Case number
CHI98IA035
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: 88dab833f00c09f83f37b48574ecbbaa6f6088d8fced66a104c1166af6a6173a; retrieved 2026-09-22T18:12:20.809Z.