FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19FA070 · Piper PA28 181

19 Dec 2018 · Blairsville, GA, United States

Piper PA28 181 · Accident: controlled flight into terrain/object (CFIT) on approach

From Blairsville Airport (DZJ) to Blairsville Airport (DZJ)

Report a problem

Event

NTSB case
ERA19FA070
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
3 · 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
Visual Meteorological Cond

Piper PA28 181

Aircraft type
Piper PA28
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
N6143J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Blairsville Airport (DZJ), Blairsville, GATo Blairsville Airport (DZJ), Blairsville, GA
Aircraft age
About 42 years (built 1976)
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
Approach · VFR pattern final
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The private pilot was approaching the airport for landing following a local personal flight in night visual meteorological conditions when the airplane impacted 60 to 70-ft-tall trees about 1/2 mile from the end of the runway. Although the runway lights were illuminated at the time of the accident, the runway was not equipped with a precision approach path indicator (PAPI) or visual approach slope indicator (VASI) light system.

Examination of the airplane and the engine did not reveal any preaccident mechanical discrepancies that would have precluded normal operation. A review of the pilot's logbook revealed that the pilot had not flown at night in just over four months preceding the accident.

It is likely that, in the absence of a PAPI or VASI system by which to judge the airplane's approach path, the sparsely-lit terrain off the approach end of the runway may have created an illusion that resulted in the pilot's descent into terrain short of the runway.

Probable cause

The pilot's failure to maintain clearance from trees during a visual approach for landing in night visual meteorological conditions. Contributing to the accident was the pilot's lack of recent experience flying at night.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19FA070
Event ID
20181219X11357
Case number
ERA19FA070
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2018-12-20.
  • API snapshot SHA-256: 10928bb31fa041c44491f344bf063dfd66d240e169d43d33bba3ef5694e4b807; retrieved 2026-09-15T06:52:10.010Z.