FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI84FA343 · Piper PA-12

12 Aug 1984 · Alpena, MI, United States

Piper PA-12 · Accident: loss of control in flight while maneuvering

From Alpena County Regional Airport (APN) to an unrecorded destination

Report a problem

Event

NTSB case
CHI84FA343
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
N98967
Operator
Unknown
Onboard fatalities
Unknown
Route
From Alpena County Regional Airport (APN), Alpena, MITo 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
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; Tree(s)
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

  • Pilot in command › Aircraft handling, improper
  • Pilot in command › Airspeed, not maintained
  • Pilot in command › Judgment, poor
  • Pilot in command › Stall/spin, inadvertent

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

NTSB narrative

WITNESSES STATED THAT THE ACFT FLEW AT A VERY LOW ALTITUDE OVER THE LAKE PERFORMING WHAT APPEARED TO BE A SERIES OF STALLS AND RECOVERIES WITH THE ACFT CLIMBING STEEPLY TO APRX 150 FT ABOVE THE LAKE AND THEN DROPPING SHARPLY BACK DOWN WITHIN A FEW FEET OF THE WATER. WITNESSES OBSERVED THE ACFT PULL UP ABRUPTLY AS IT REACHED THE SOUTH SHORELINE WHERE A FOREST OF TREES WERE GROWN TO APRX 100 FT.WITNESSES STATED THAT THE ACFT APPEARED TO STALL AND ROLL SHARPLY TO THE LEFT, DESCENDING INTO THE TREES. THERE WAS NO EVIDENCE OF A MECHANICAL MALFUNCTION OR FAILURE OF THE ACFT STRUCTURE, FLT CONTROLS, ENG OR PROP PRIOR TO IMPACT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record CHI84FA343
Event ID
20001214X40608
Case number
CHI84FA343
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: 5094c30876899bca3164f45c8bbc4f7f4bb5c0f0fc56170f9085ac4c9d748f2a; retrieved 2026-09-21T05:23:48.658Z.