FTW98FA117 · Piper PA-34-200
Piper PA-34-200 · Accident: in flight collision with terrain/water en route
From F54 · Arlington, TX to Possum Kingdom Airport (F35)
Event
- NTSB case
- FTW98FA117
- 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
- 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-34-200
- Aircraft type
- Piper PA-34
- 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
- N15566
- Operator
- Fred H. Pate · private individual
- Onboard fatalities
- Unknown
- Route
- From F54 · Arlington, TXTo Possum Kingdom Airport (F35), TX
- 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 · cruise
- 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 terrain/water
- 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 › Clearance, not maintained
Approximate · Estimated position: the centre of Graford, TX, the place the record names. Not the accident site.
NTSB narrative
The airplane was dispatched to pick up a stranded flightcrew that landed at the destination airport, 70 miles from home base. Fog had formed in the area. The airplane circled the airport, above the fog layer, but was unable to land due to the fog. After circling the airport, the airplane was heard proceeding east bound until the sound of the engines disappeared. An ELT signal was received by another airplane on the 290 degree radial, 19 miles from the Milsap VOR. There were no reported eyewitnesses. The wreckage was located the next morning on the eastern ledge of a granite ridgeline of a north-south oriented hill rising approximately 200 feet above the surrounding terrain. The wreckage was scattered for 270 feet on a heading of 240 degrees. Signatures at the initial point of impact indicate that the airplane contacted trees and terrain in controlled flight in a slight left wing down attitude. Flight control continuity was established. The landing gear and flaps were found in the retracted position.
Probable cause
The pilot's failure to maintain clearance with the ground. Factors were the dark night, the rising terrain, and the ground fog obscuring the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98FA117
- Event ID
- 20001211X09536
- Case number
- FTW98FA117
- 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 1998-02-04.
- API snapshot SHA-256: ecca01b0a5bd56a4ec59d3b8052802fda002e71f22746e84ba25f645f85adef2; retrieved 2026-09-20T22:41:12.550Z.