FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

J & M Alaska Air Tours Piper PA 31-350 accident

16 May 2015 · Homer, AK, United States

Piper PA 31-350 · Accident: landing gear not configured

From Tatitlek Airport (7KA) to Homer Airport (HOM)

Report a problem

Event

NTSB case
ANC15CA027
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
Charter & commuter
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 31-350

Aircraft type
Piper PA-31
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
N4079H
Onboard fatalities
Unknown
Route
From Tatitlek Airport (7KA), TATITLEK, AKTo Homer Airport (HOM), Homer, AK
Aircraft age
About 34 years (built 1981)
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 135: Air Taxi & Commuter
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
Landing
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
Landing gear not configured
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 systems
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was landing a retractable landing gear-equipped, twin engine airplane at an uncontrolled airport. While on final approach, an airplane that landed in front of him reported a moose in the vicinity of the runway. An airport maintenance person announced on the common traffic advisory frequency (CTAF) that he was attempting to chase the moose off of the runway. The pilot became distracted trying to avoid wake turbulence from the preceding airplane and monitor the location of the vehicle and moose and failed to extend the landing gear prior to landing. During touchdown, the airplane contacted the runway with the landing gear retracted, and it slid about 1,200 feet. The airplane sustained substantial damage to the fuselage. The pilot stated that there were no preaccident mechanical anomalies with the airplane that would have precluded normal operation.

Probable cause

The pilot's failure to extend the landing gear before landing. Contributing to the accident was the pilot's decision to continue the approach to landing while distracted and his failure to complete the landing checklist.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC15CA027
Event ID
20150526X10116
Case number
ANC15CA027
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2015-05-17.
  • API snapshot SHA-256: b2085696affe159d47a4254680f96d45ad99e5cef43d1cd6e6162b509a41471b; retrieved 2026-09-16T02:20:49.103Z.