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

May 15, 2003 · Rotorway Exec 162F · N212DP

Longview, TX

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 15, 2003
Injury Outcomes
No injuries (1 uninjured)
Location
Longview, TX
Aircraft
Rotorway Exec 162F
Tail Number
N212DP
Injuries
None
Aircraft Damage
Substantial
NTSB Number
FTW03LA153

The 269-hour pilot attempted to contact the air traffic control tower when the aircraft was approximately 250 feet agl. The pilot stated as he pressed the push to talk (PTT) button on the cyclic control, the "engine had a flame out." Due to obstacles in the flight path of the helicopter, the pilot was forced to turn the helicopter and "attempt a landing on a downhill slope." During the landing, the turbine powered helicopter nosed over and came to rest on its right side. During a telephone interview, the pilot reported to the NTSB investigator-in-charge that he was having problems with the radio and installed a new one prior to departing. The pilot stated that after takeoff he pressed the PTT and it "caused the ignition system to go out."

NTSB Probable Cause

The failure of the engine ignition system for undetermined reasons resulting in a loss of engine power. A contributing factor was the lack of suitable terrain for an auto rotational landing.

Full Narrative

On May 15, 2003, at 1530 central daylight time, a Rotorway Exec 162F helicopter, N212DP, registered to and operated by a private individual, sustained substantial damage during a forced landing following a loss of engine power near Longview, Texas. The private pilot, who was the sole occupant of the helicopter, was not injured. Visual meteorological conditions prevailed, and a flight plan was not filed for the 14 Code of Federal Regulations Part 91 personal flight. The local flight departed from a private residence approximately 10 minutes prior, and was destined for the East Texas Regional Airport (GGG), near Longview, Texas. The 269-hour pilot reported in the NTSB Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2) that he climbed to an altitude of approximately 250 feet agl, and attempted to contact the air traffic control tower at GGG on the radio. The pilot stated as he pressed the push to talk (PTT) button on the cyclic control, the "engine had a flame out." He immediately entered an autorotation, and selected a landing area. Due to obstacles in the flight path of the helicopter, he was forced to turn the helicopter and "attempt a landing on a downhill slope." During the landing, the helicopter nosed over and came to rest on its right side. During a telephone interview, the pilot reported to the NTSB investigator-in-charge that he was having problems with the radio and installed a new one prior to the accident flight. He stated that after takeoff he pressed the PTT and it "caused the ignition system to go out." Examination of the turbine-powered helicopter by an FAA inspector, who responded to the accident site, revealed both main rotor blades were damaged. The tail boom was bent, and the aft three feet of the tail boom was separated.

Flight

Event TypeAccident
Event Time15:30 CDT
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftRotorway Exec 162F
Tail NumberN212DP
Aircraft CategoryHeli
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeTurboshaft
Engine DetailsInternational Harvester · Solar T-62T-3 · Turboshaft · 150
Seats2

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 66 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind190°
Visibility10 sm
CeilingNone
Temperature / Dew Point70 F
Altimeter29.79 inHg
Weather SourcePILO

Appendix: Source Data