Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

July 10, 2004 · Hughes 269C · N56PH

Arlington, WA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 10, 2004
Injury Outcomes
No injuries (2 uninjured)
Location
Arlington, WA
Aircraft
Hughes 269C
Tail Number
N56PH
Injuries
None
Aircraft Damage
Substantial
NTSB Number
SEA04LA128

While cruising at about 2,500 feet above the ground (agl), the pilot heard a "pop" and felt the helicopter yaw to the right. Almost immediately he noticed that the engine was starting to lose power, and he therefore lowered the collective and initiated a partial autorotation. He then attempted to get the engine to accelerate, but he continued to hear "sputtering and popping," and the engine continued to gradually lose power. The pilot therefore elected to perform a full autorotational landing in a nearby opening in the heavily wooded area he was flying over. Although he was able to touch down with only a very slow forward speed, the terrain he was landing on turned out to be a wet and muddy bog or swamp, and as the helicopter touched down, one of the skids sunk into the mud, and the aircraft rolled over onto its side. A post-accident inspection of the helicopter's engine and fuel system by an FAA Airworthiness Inspector and a fixed base operator's (FBO's) maintenance personnel did not find any evidence of an anomaly that would have lead to a loss of power in the engine. After the initial inspection was completed, the engine was mounted on an engine stand and run at various speeds for a period of about eight minutes. During the test run, the engine started easily and ran smooth at all tested speeds up to and including a maximum of 3,100 rpm.

NTSB Probable Cause

A significant power loss for undetermined reasons while in cruise flight, leading to a full autorotational landing. Factors include no suitable terrain in the area, and soft swampy terrain at the point where the pilot found it necessary to perform the forced landing.

Full Narrative

On July 9, 2004, approximately 2010 Pacific daylight time, a Hughes 269C helicopter, N56PH, impacted the terrain during an attempted autorotational landing about 12 miles north of Arlington, Washington. The commercial pilot and his passenger were not injured, but the aircraft, which is owned and operated by the pilot, sustained substantial damage. The 14 CFR Part 91 personal pleasure flight, which departed Bellingham, Washington, about 55 minutes prior to the accident, was being operated in visual meteorological conditions. The flight was en route to Arlington, Washington. No flight plan had been filed. According to the pilot, while cruising at about 2,500 feet above the ground (agl), he heard a "pop" and felt the helicopter yaw to the right. Almost immediately he noticed that the engine was starting to lose power, and he therefore lowered the collective and initiated a partial autorotation "...to take demands off the engine." He then attempted to get the engine to accelerate, but he continued to hear "sputtering and popping," and the engine continued to gradually lose power. The pilot therefore elected to perform a full autorotational landing in a nearby opening in the heavily wooded area he was flying over. Although he was able to touch down with only a very slow forward speed, the terrain he was landing on turned out to be a wet and muddy bog or swamp, and as the helicopter touched down, one of the skids sunk into the mud, and the aircraft rolled over onto its side. A post-accident inspection of the helicopter's engine and fuel system by an FAA Airworthiness Inspector and maintenance personnel from Precision Helicopters did not find any evidence of an anomaly that would have contributed to a loss of power in the engine. After the initial inspection was completed, the engine was mounted on an engine stand and run at various speeds for a period of about eight minutes. During the test run, the engine started easily and ran smooth at all tested speeds up to and including a maximum of 3,100 rpm.

Flight

Event TypeAccident
Event Time20:10 PDT
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftHughes 269C
Tail NumberN56PH
Aircraft CategoryHeli
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · HIO-360-D1A · Reciprocating · 190
Seats2

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 59 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind310° @ 5 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point61 F / 0 C
Altimeter0
Weather SourcePILO

Appendix: Source Data