- Date
- July 25, 2009, 02:30 local (12:30 UTC)
- Place
- Kaunakakai, HI
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N691TS.C. Aerostar YAK-52W
- Defining event
- Approach-VFR pattern downwind: Controlled flight into terr/obj (CFIT)
- Weather
- Visual (VMC) · Night/dark
- Status
- Completed · report July 1, 2010
- Report
- Approved by Office Director
- NTSB office
- Western Pacific Region
- Parties
- Federal Aviation Administration
- FAA report
- 20090725054039A
- Case key
- 75683
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The pilot's failure to maintain clearance from terrain while in the airport traffic pattern in dark night conditions.
Findings · 3
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
The pilot reported that he was returning to his home airport in dark night conditions. He performed a low approach, about 50 feet above the runway, to clear it of any wildlife that may have been present. After turning into the crosswind leg, he turned off the landing lights due to a high ambient glare that left him with a partial loss of night vision for a few seconds. He also stated that he neglected to set the elevator trim to maximum up, and that he had maintained a full cruise power setting. He reported that the altimeter was dark and not readable after he turned into the downwind leg of the approach. Shortly afterward the airplane unexpectedly contacted the ground, which resulted in structural damage to both wings and the fuselage. The airplane came to rest in an upright position in a nose-down attitude. The downwind portion of the traffic pattern is on a gradual slope that is about 200 feet higher than the runway. The pilot reported that he had made numerous night landings to his home airport. On the accident landing he did not cross-check the altimeter during the approach and had not properly configured the airplane for landing. He added that if he would have followed his normal regimen, and configured the airplane properly, the airplane would have been about 1,000 feet higher than it was when it impacted the terrain. The pilot reported that there were no mechanical problems with the airframe or engine at the time of the accident.
Factual narrative
The pilot reported that he was returning to his home airport in dark night conditions. He performed a low approach, about 50 feet above the runway, to clear it of any wildlife that may have been present. After turning crosswind, he turned off the landing lights due to a high ambient glare that left him with a partial loss of night vision for a few seconds. He also stated that he neglected to set the elevator trim to maximum up, and that he had maintained a full cruise power setting. He reported that the altimeter was dark and not readable after he turned onto downwind. Shortly after turning onto the downwind, the airplane unexpectedly contacted the ground, which resulted in structural damage to both wings and the fuselage. The airplane came to rest in an upright position in a nose down attitude. The downwind portion of the traffic pattern is on a gradual slope that is about 200 feet higher than the runway. The pilot reported that he had made numerous night landings to his home airport. On the accident landing he did not cross-check the altimeter during the approach, and had not properly configured the airplane for landing. He added that if he would have followed his normal regimen, and configured the airplane properly, the airplane would have been about 1,000 feet higher than it was when it impacted the terrain. The pilot reported that there were no mechanical problems with the airframe or engine at the time of the accident.
Aircraft
- Registration
- N691T
- Reported as
- S.C. Aerostar YAK-52W
- Category
- Airplane
- Serial number
- 9912202
- Airframe hours
- 540
- Engine
- Vedeneyev M14P, 360 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- John Hutton Corp
- Registered owner
- John Hutton Corp
- Airworthiness certificate
- Special, Experimental (Special); Standard, Utility; Special, Restricted (Special); Standard, Aerobatic; Standard, Normal
- Last inspection
- Annual · June 5, 2009 · 19 hours before
- Departed
- HNL · Honolulu, HI
- Destination
- HI49 · Kaunakakai, HI
- Airport
- HI49 · Panda Airport
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 74
- Injuries
- None
- Certificates
- Commercial, Private
- Airplane ratings
- Multi-engine land, Single-engine sea, Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 2, Without waivers/limitations
- Last flight review
- January 16, 2010
- Seat
- Front
- Flight hours
- 22,000 total · 330 in this make and model
Weather
- Conditions
- Visual (VMC) · Night/dark
- Wind
- Calm
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 79 °F, dew point 70 °F
- Altimeter
- 29.92 inHg
- Observed at
- HNL, 40 nm away
Docket · 1
The files NTSB released with the investigation on June 1, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 312 KB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.