- Date
- December 15, 1972
- Place
- Festus, MO · FESTUS, MO
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N3808TPiper PA-28R
- Status
- Completed · report March 24, 1973
- Report
- Brief approved by the director
- Case key
- 168846
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-3552 72/12/15 FESTUS,MO PIPER PA-28R CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 40, 475 TIME - 1500 N3808T PX- 0 0 1 BUSINESS TOTAL HOURS, 250 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - FESTUS DEPARTURE POINT INTENDED DESTINATION DALLAS,TEX ST.LOUIS,MO TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES LANDING: FINAL APPROACH COLLIDED WITH: FENCE,FENCEPOSTS LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS FACTOR(S) PILOT IN COMMAND - EXERCISED POOR JUDGMENT WEATHER - TURBULENCE, ASSOCIATED W/CLOUDS AND/OR THUNDERSTORMS TERRAIN - HIGH OBSTRUCTIONS SKY CONDITION CEILING AT ACCIDENT SITE SCATTERED UNLIMITED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE WIND DIRECTION-DEGREES NONE 280 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 17 VFR TYPE OF FLIGHT PLAN NONE REMARKS- PILOT MISTOOK DRAG STRIP FOR ARPT. RELIED ON NONPILOT PSGR TO IDENTIFY ARPT.
Aircraft
- Registration
- N3808T
- Reported as
- Piper PA-28R
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Festus
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.