FTW73FRA13

NTSB accident investigation · Piper PA-28 · Bellville, TX · December 27, 1972

Accident · No injuriesClosed
Date
December 27, 1972
Place
Bellville, TX · BELLVILLE, TX
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N4119JPiper PA-28
Status
Completed · report March 29, 1973
Report
Brief approved by the director
Case key
169287

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-3875  72/12/27   BELLVILLE,TEX       PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 25, 196
        TIME - 2020                    N4119J              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 69 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - GRAWUNDER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS

Aircraft

Registration
N4119J
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Grawunder

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.