FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16LA252 · Piper PA-22-150

2 Jul 2016 · Houghton Lake Heights, MI, United States

Piper PA-22-150 · Accident: collision during takeoff/landing on approach

From Houghton Lake State Airport (5Y2) to Houghton Lake State Airport (5Y2)

Report a problem

Event

NTSB case
CEN16LA252
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-22-150

Aircraft type
Piper PA-22
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
N5788D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Houghton Lake State Airport (5Y2), Houghton Lake Heights, MITo Houghton Lake State Airport (5Y2), Houghton Lake Heights, MI
Aircraft age
About 60 years (built 1956)
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
Approach · VFR pattern final
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
Collision during takeoff/landing
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 oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena

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

NTSB narrative

The private pilot reported that the purpose of the flight was to provide the passengers with an introductory flight in conjunction with an event hosted by a local chapter of the Experimental Aircraft Association. He stated that there were no mechanical issues or anomalies with the airplane during an earlier flight. After departure, the airplane climbed to 2,500 ft mean sea level, and the pilot completed a local flight before entering the traffic pattern for a full-stop landing on runway 34. The pilot reported that, while on final approach, as the airplane passed over a tree line, it encountered a downdraft and descended below the normal glidepath. As he increased engine power to arrest the airplane's descent, the main landing gear struck a wire fence near the approach end of the runway. The airplane subsequently landed hard on its nose landing gear, which collapsed the nose gear, and skidded to a stop in a nose-down attitude on the runway. The pilot reported that there were no mechanical failures or malfunctions with the airplane that would have precluded normal operation.

A postaccident review of available meteorological data established that the surface wind was likely variable from the southwest to northwest at 5 to 8 knots. Although the variable wind condition had the potential to develop minor turbulence and an associated downdraft during the final approach, the pilot should have been able to anticipate and adequately handle the variable wind condition. It is likely that the pilot's delayed reaction to the variable wind condition resulted in an excessive descent rate and the airplane's subsequent collision with the wire fence short of the runway.

Probable cause

The pilot's delayed reaction to the variable wind condition, which resulted in an excessive descent rate and the airplane's subsequent collision with a wire fence short of the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16LA252
Event ID
20160707X02810
Case number
CEN16LA252
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: 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: add4cc24956feca6e7148693e5fc20c7062eef72493a178afcf574117d43fc79; retrieved 2026-09-16T03:37:45.345Z.