FTW66D0623

NTSB accident investigation · Cessna 172 · Freemason Is, LA · April 8, 1966

Accident · No injuriesClosed
Date
April 8, 1966
Place
Freemason Is, LA · FREEMASON IS, LA
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7967BCessna 172
Status
Completed · report June 13, 1966
Report
Brief approved by the director
Case key
172082

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-0937   66/4/8    FREEMASON IS LA     CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 38, 180
        TIME - 1700                    N7967B              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 119 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FREEMASON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: HIDDEN HAZARD
        REMARKS- DITCH 300 FEET FROM END OF RUNWAY ON PRIVATE AIRSTRIP

Aircraft

Registration
N7967B
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Freemason

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.