FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL82DA177 · Piper PA-22-150

26 Jun 1982 · HIXSON, TN, United States

Piper PA-22-150 · Accident: in flight collision with object on approach

From 1A0 · HIXSON, TN to 1A0 · HIXSON, TN

Report a problem

Event

NTSB case
ATL82DA177
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
0 · all aircraft and ground
Ground fatalities
0
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 PA-22-150

Aircraft type
Piper PA-22
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
N2604P
Operator
James G. Godsey · private individual
Onboard fatalities
Unknown
Route
From 1A0 · HIXSON, TNTo 1A0 · HIXSON, TN
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
Approach · VFR pattern final
First occurrenceThe 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
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Pilot in command › Judgment, poor

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PILOT ELECTED TO TAKEOFF ON A DARK NIGHT WITHOUT RUNWAY LIGHTS. HE STATED THAT THE RUNWAY LIGHTS WERE NOT AVAILABLE AT THE TIME SINCE THE OPERATOR WAS OUT OF TOWN. ACCORDING TO THE PILOT AND OTHER WITNESSES, AT LEAST PART OF THE AIRPORT ENVIRONMENT WAS ILLUMINATED BY THE LIGHTS NEAR THE APPROACH END OF RUNWAY 23. THE PILOT REPORTED THAT HE CLIMBED STRAIGHT AHEAD TO 400 FT AGL AFTER TAKING OFF FROM RUNWAY 23. REPORTEDLY AT THAT ALTITUDE, HE TURNED RIGHT, THEN BACK LEFT, INTENDING TO LAND ON RUNWAY 05. HE SAID THAT HE TURNED TO WHERE HE EXPECTED TO FIND THE RUNWAY AND BEGAN HIS DESCENT. THE LANDING LIGHT WAS NOT AS BRIGHT AS HE ANTICIPATED, THE VISIBILITY WAS RESTRICTED SLIGHTLY BY HAZE, AND THE BRIGHT LIGHTS OF THE BALL PARK MADE IT DIFFICULT TO SEE. ALSO, HE REPORTED THAT MANY OF THE BALL PARK LIGHTS WERE TURNED OFF CAUSING A BLACK AREA WHICH WAS DISORIENTING. WHILE DESCENDING TO RUNWAY 05,THE PLANE STRUCK A TREETOP AND CAME TO REST IN A WOODED AREA.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL82DA177
Event ID
20020917X02762
Case number
ATL82DA177
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1982-06-27.
  • API snapshot SHA-256: 50ed37ff5b51d65ac2971833d072bf8ec9a6a8b7f29a1459e1a085cfcd71a6f0; retrieved 2026-09-22T03:00:55.530Z.