FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC09CA048 · Piper PA-32-301

15 May 2009 · Birchwood, AK, United States

Piper PA-32-301 · Accident: part(s) separation from aircraft en route

From Merrill Field (MRI) to Birchwood Airport (PABV)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ANC09CA048
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
Unknown
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-32-301

Aircraft type
Piper PA-32
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
N8374T
Onboard fatalities
Unknown
Route Possible conflict
From Merrill Field (MRI), Merrill Field, AKTo Birchwood Airport (PABV), Birchwood, AK
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 · cruise
Defining eventThe 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
Part(s) separation from aircraft
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

  • Aircraft › Aircraft structures
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airline transport pilot was ferrying the airplane under Title 14, CFR Part 91, to an airport to be painted. During cruise flight, the upper portion of the aft cargo door separated from the airplane, striking the horizontal stabilator. The pilot said he believed the door was latched securely prior to the flight. The flight continued to the destination airport and landed uneventfully. An examination of the fuselage-mounted upper door latch by an FAA inspector showed that the upper portion of the latch striker plate was missing, and the door locking mechanism was not properly aligned with the latch. The FAA inspector noted that it appeared that the missing portion of the latching plate had been missing long before the accident, and should have been found on routine maintenance inspections. The upper portion of the door was not recovered. The airplane sustained substantial damage to the stabilator.

Probable cause

The failure of maintenance personnel to properly maintain the cargo door latch, resulting in an in-flight opening and separation of the cargo door, and substantial damage to the horizontal stabilator when it was struck by remnants of the cargo door.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC09CA048
Event ID
20090526X95935
Case number
ANC09CA048
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2009-05-16.
  • API snapshot SHA-256: fa80f747435f166e8d06a54a71cfc34fd279a279c94ee613d475248045b8c504; retrieved 2026-09-15T11:12:26.168Z.