FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02FA049 · Piper PA-24-250

13 Jan 2002 · Micanopy, FL, United States

Piper PA-24-250 · Accident: loss of control in flight while maneuvering

From Gainesville Regional Airport (GNV) to Williston Municipal Airport (X60)

Report a problem

Event

NTSB case
MIA02FA049
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
Visual Meteorological Cond

Piper PA-24-250

Aircraft type
Piper PA-24
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
N8263P
Onboard fatalities
Unknown
Route
From Gainesville Regional Airport (GNV), Gainesville, FLTo Williston Municipal Airport (X60), Williston, FL
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
Maneuvering
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
Loss of control in flight
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
Destroyed

Cause areas

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Spatial disorientation

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

NTSB narrative

An individual with Flightline Inc., at Gainesville Regional Airport, stated that he refueled N8263P, and at the pilot's request, he added 30 gallons of fuel. He stated that the pilot said he wanted the extra fuel as a safety precaution, but elected not to "top-off" the airplane. According to the refueler, at the time he was refueling the accident airplane, the clouds were low, and there was light rain. He further stated that he heard the two occupants of the airplane state that they had just flown from Pennsylvania, and they joked about being tired, and "dragging", after being in the airplane for such a long time. He further stated that they were concerned about leaving, and said about two or three times that they were too close to their final destination of Williston, Florida, and they did not want to stay in Gainesville, Florida. According to an official with the FAA Gainesville Flight Service Station, the flight departed early Sunday morning, and during the departure, the pilot stated that he was "departing VFR to the south." There was no further communications with the pilot of the accident airplane. Near the time of the accident, the visibility and cloud conditions reported at the Gainesville Regional Airport were visibility 10 statute miles and the sky condition was scattered clouds at 2200 feet and 3000 feet with broken clouds at 10000 feet. According to radar data obtained from the Cross City, Florida ARSR-4 radar facility, the airplane departed Gainesville Regional Airport at approximately 0035 and proceeded in the direction of Williston, Florida. Radar data shows that the flight path of the airplane consisted of numerous course changes, altitude variations between 1900 feet and 800 feet, and groundspeed variations between approximately 150 knots and 91 knots over a period of about 13 minutes from departure until radar contact was lost. Examination of the last 36 seconds of radar data shows the airplane in a right hand descending turn. During the period from 12 seconds, until the loss of radar contact, the average rate of descent and groundspeed were 2500 feet per minute and 150 knots respectively. The airplane was at an altitude of about 800 feet when radar contact was lost. The airplane struck a tree at approximately the fifty foot level, impacting the ground at about a 20 degree angle approximately 150 feet from the tree. The debris field was about 300 feet long, and oriented along a heading 312 degrees. Examination of the airplane's engine, flight controls, and airframe did not reveal any evidence of preaccident anomalies.

Probable cause

The pilot's experiencing spatial disorientation while maneuvering at a low altitude at night under visual meteorological conditions which resulted in an uncontrolled descent and an in-flight collision with a tree.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02FA049
Event ID
20020122X00091
Case number
MIA02FA049
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: 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: 4ea3c3b722b4a3927f554e92c8e1b8ad37781d2e1cb0c9959789491d437bbf69; retrieved 2026-09-20T20:14:36.944Z.