FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09LA123 · Piper PA-28-151

3 Jan 2009 · Powder Springs, TN, United States

Warrior Aviation Piper PA-28-151 · Accident: controlled flight into terrain/object (CFIT) en route

From Gatlinburg-Pigeon Forge Airport (GKT) to Warsaw Municipal Airport (ASW)

Report a problem

Event

NTSB case
ERA09LA123
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
2 · 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
Instrument Meteorological Cond

Piper PA-28-151

Aircraft type
Piper PA-28
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
N43631
Onboard fatalities
Unknown
Route
From Gatlinburg-Pigeon Forge Airport (GKT), Sevierville, TNTo Warsaw Municipal Airport (ASW), Warsaw, IN
Aircraft age
Not recorded
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
En route
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
Controlled flight into terrain/object (CFIT)
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

  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

After departing the traffic pattern and turning toward mountainous terrain, the airplane entered instrument meteorological conditions (IMC). The pilot had some training for his instrument rating but did not yet possess one. A witness who resided near the accident location heard the airplane traveling in a northerly direction and impact terrain. He reported that, the "weather was overcast," and he could not see the tops of the mountains. He estimated that the cloud base at the time was about 100 to 200 feet below the tops of the mountains. Review of a weather briefing which was obtained by the pilot revealed that he was advised that flight under visual flight rules was not recommended due to low ceilings and visibility along the route of flight and that the pilot had declined to file a flight plan. Additionally, no evidence was discovered that indicated the pilot had attempted to receive updated weather information prior to the accident flight, or that he had contact with air traffic control. Examination of the airplane revealed no evidence of any preimpact malfunctions or failures.

Probable cause

The non-instrument rated pilot's decision to continue under visual flight rules into an area of instrument meteorological conditions, which resulted in an in-flight collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09LA123
Event ID
20090103X93911
Case number
ERA09LA123
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, coordinates. 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: 33d34b70430a1066852903dcd4093d108c1c111aaea6a22fd284ff7836085345; retrieved 2026-09-13T19:53:44.946Z.