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

February 19, 2009 · Piper PA-31-350 · N41185

Nome, AK

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 19, 2009
Injury Outcomes
6 injuries (1 serious injury, 5 minor injuries)
Location
Nome, AK
Aircraft
Piper PA-31-350
Tail Number
N41185
Operator
Frontier Flying Service
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
ANC09LA021

The scheduled commuter flight was about 10 miles north of the destination airport, operating under a special visual-flight-rules clearance, and descending for landing in instrument meteorological conditions. According to the pilot, he started a gradual descent over an area of featureless, snow-covered, down-sloping terrain in whiteout and flat light conditions. During the descent, a localized snow shower momentarily reduced the pilot’s forward visibility and he was unable to discern any terrain features. The airplane collided with terrain in an all-white snow/ice field and sustained substantial damage. At the time of the accident, the destination airport was reporting visibility of 1.5 statute miles in light snow and mist, broken layers at 900 and 1,600 feet, and 3,200 feet overcast, with a temperature and dew point of 25 degrees Fahrenheit. The pilot reported that there were no preaccident mechanical problems with the airplane and that the accident could have been avoided if the flight had been operated under an instrument-flight-rules flight plan.

NTSB Probable Cause

The pilot's continued flight into adverse weather and his failure to maintain clearance from terrain while on approach in flat light conditions.

Full Narrative

On February 19, 2009, about 1812 Alaska standard time, a twin-engine Piper PA-31-350 airplane, N41185, sustained substantial damage when it collided with snow-covered terrain about 5 miles northeast of the Nome Airport, Nome, Alaska. The airplane was being operated by Frontier Flying Service, Fairbanks, Alaska, as a visual flight rules (VFR) scheduled domestic commuter flight, as Flight 8218, under the provisions of Title 14 Code of Federal Regulations (CFR) Part 135. Of the six people aboard, the airline transport pilot and four passengers sustained minor injuries, and one passenger sustained serious injuries. Instrument meteorological conditions prevailed at the airport, and company flight following procedures were in effect. The flight departed Brevig Mission, Alaska, about 1735, en route to Nome. During a conversation with the National Transportation Safety Board investigator-in-charge on February 20, the pilot reported that just after leaving Brevig Mission, he climbed the airplane to 5,500 feet, but as the flight progressed south towards Nome, the ceiling began to lower, and visibility diminished. About 10 miles north of Nome, the pilot said that he descended to about 1,500 feet, and the visibility was between 1 to 2 miles, with light snow showers. The pilot said he contacted the Nome Flight Service Station (FSS), about 8 miles north of Nome, and obtained an airport advisory. The FSS specialist on duty reported that current weather conditions at the airport were below basic VFR conditions, then asked the pilot his intentions. The pilot reported that he requested and received a Special VFR clearance to enter the Nome Class E airspace, and he was advised that runway 28 was in use. He said that as the airplane flew towards the Nome Airport, he lowered the landing gear, configured the flaps to the approach setting, and started a gradual descent over an area of featureless, snow-covered, down-sloping terrain. The pilot said that during the descent a localized snow shower momentarily reduced his forward visibility, which deteriorated to a point where he was unable to discern any terrain features. He added that "flat light conditions" contributed to his inability to recognize any topographical features on the snow-covered terrain. The pilot said that he then encountered what he described as "white-out conditions," and the airplane subsequently collided with the snow-covered terrain. After the airplane struck terrain, the main landing gear collapsed, and the airplane slid for about 100 feet, coming to rest in 8 feet of fresh, windblown snow. The closest weather reporting facility was the Nome Airport, 5 miles southwest of the accident site. At 1802, about 10 minutes before the accident, a special weather observation from the Nome Airport was reporting, in part: Wind, 250 degrees (true) at 20 knots, gusting to 25 knots; visibility, 1.5 statute miles with light snow and mist; clouds and sky condition, broken layers at 900 and 1,600 feet, 3,200 feet overcast; temperature, 25 degrees F; dew point, 25 degrees F; altimeter, 30.06 inHg. At 1821, about 24 minutes after the accident, a special weather observation from the Nome Airport was reporting, in part: Wind, 270 degrees (true) at 8 knots; visibility, 1.25 statute miles with light snow and mist; clouds and sky condition, 1,100 feet scattered, 2,200 feet overcast; temperature, 21 degrees F; dew point, 21 degrees F; altimeter, 30.09 inHg. The pilot reported that there were no preaccident mechanical problems with the airplane, and noted in his written report to the NTSB that the accident would have been avoided if the flight had been operated under an instrument flight rules flight plan. SEARCH AND RESCUE After being notified of an overdue airplane and learning that the airplane’s last reported position was about 7 miles northeast of the Nome Airport, search and rescue personnel from the Nome Fire Department, Nome Search and Rescue Group, and the Alaska State Troopers, began a ground search for the missing airplane using snow machines. A helicopter from Nome was dispatched to join the search, but low clouds, snow, and reduced visibility prevented the crew from continuing the aerial search. According to the Alaska State Troopers, about 2100, ground searchers reported seeing a set of dim glimmering lights in an area of mountainous terrain. As the searchers approached the lights they discovered that they were from flashlights that the airplane’s occupants were using to signal the approaching searchers. The pilot and passengers were transported to a nearby road via snow machine, then by ambulance to Nome. Emergency Locator Transmitter (ELT) The accident airplane was not equipped with a 406 MHz ELT, which can be detected within seconds by geostationary search and rescue satellites, and provide searchers with accurate global positioning system coordinates. According to the operator’s director of flight safety, the accident airplane had an older generation 121.5 MHz ELT installed. Both types of ELT’s can be turned on manually, or automatically, by impact forces. Effective February 1, 2009, 19 days before the accident, world-wide satellite monitoring of 121.5 MHz ELT’s was terminated, due in part because of their many false reports, lack of accuracy, and low power and range when compared to the 406MHz ELT. Now 121.5 MHz ELT’s can only be detected by ground-based receivers such as some airport facilities and air traffic control facilities, or by overflying aircraft, greatly diminishing their effectiveness. The decision to terminate satellite monitoring of 121.5 MHz ELT’s was made in October 2000, in response to guidance from the International Civil Aviation Organization, giving aircraft owners and operators more than 8 years notice to replace their older 121.5 MHz ELT’s with 406 MHz ELT’s. Although the NTSB has made two prior recommendations to the FAA seeking that they mandate the use of 406 MHz ELT’s, it is still legal to operate both non-commercial and commercial flights without a 406 MHz ELT.

Flight

Event TypeAccident
Event Time13:12 AKST
Nearest AirportNOME (5nm)
Runway28
Runway Length6001 ft
Runway Width150 ft
Flight Plan FiledCvfr
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-31-350
Tail NumberN41185
Aircraft CategoryAir
DamageSubstantial
OperatorFrontier Flying Service
Operating RulePart 135
Engines2
Engine TypeReciprocating
Engine DetailsLycoming · T10-540-J2B · Reciprocating · 350 | Lycoming · LT10-540-J2B · Reciprocating · 350
Seats7

People & Injuries

Injury Summary6 injuries (1 serious injury, 5 minor injuries)
Fatal0
Serious1
Minor5
Uninjured0
Total6
Crew 1Age 66 · First Class · Minor

Conditions

ConditionsIMC
LightDusk
Wind250° @ 20 kt, gusting 25 kt
Visibility2 sm
CeilingBroken clouds 900 ft
Temperature / Dew Point25 C / 25 C
Altimeter30.05 inHg
Observation Time22:02
Weather SourceWFAC

Appendix: Source Data