FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC83FA064 · Piper PA-12

2 Apr 1983 · GLENNALLEN, AK, United States

Piper PA-12 · Accident: loss of control in flight en route

From LAKE LOUISE, AK to an unrecorded destination

Report a problem

Event

NTSB case
ANC83FA064
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
2 · 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

Piper PA-12

Aircraft type
Piper PA-12
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
N2826M
Operator
Unknown
Onboard fatalities
Unknown
Route
From LAKE LOUISE, AKTo 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
En route · climb to cruise
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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/spin
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

  • Flt control syst, elevator control › Foreign object
  • Flt control syst, elevator control › Movement restricted

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

NTSB narrative

WITNESSES REPORTED THAT AFTER TAKEOFF, THE PLT FLEW BY A CABIN AT APPROXIMATELY 200 FT, SIGNALED BY ROCKING THE ACFT'S WINGS, THEN BEGAN A GRADUAL CLIMB. THE CLIMB INCREASED IN STEEPNESS UNTIL 1 WITNESS COULD SEE THE ENTIRE TOP OF THE ACFT. IT THEN NOSED OVER, MADE 1 1/2 TO 2 1/2 TURNS & CRASHED. AN INVESTIGATION REVEALED NO SPECIFIC PREIMPACT MALFUNCTION OR FAILURE. HOWEVER, AN INVESTIGATION REVEALED THAT ACFT HAD RECEIVED 3 MAJOR MODIFICATIONS, 2 OF WHICH WERE UNDER SUPPLEMENTAL TYPE CERTIFICATES (STC'S). A MODIFIED ELEVATOR BELLCRANK HAD BEEN INSTALLED, BUT THERE WAS NO FLOOR OR PROTECTIVE COVERING INSTALLED OVER THE BELLCRANK. ONLY A CANVAS BARRIER PROTECTED THE BELLCRANK FROM ITEMS PLACED IN THE BAGGAGE COMPARTMENT. THE EDGES OF THE CANVAS DID NOT EXTEND TO THE SIDES, TOP & BOTTOM OF THE FUSELAGE, BUT INSTEAD, THERE WAS A 2 TO 3 INCH CAP, LACED WITHE STRING TO HOLD THE CANVAS SECURE. A WHISK BROOM WAS FOUND IN THE PROXIMITY OF THE ELEVATOR BELLCRANK.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ANC83FA064
Event ID
20001214X42571
Case number
ANC83FA064
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: b2b13f5e855e8c6ad64ff60e336f55e6481ea50f8f9070a3d73dfb8c364a89c2; retrieved 2026-09-21T06:58:50.266Z.