NYC67F0516

NTSB accident investigation · Cessna P206A · Laconia, NH · February 3, 1967

Accident · Serious injuriesClosed
Date
February 3, 1967
Place
Laconia, NH · LACONIA, NH
Injuries
1 serious
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N2511XCessna P206A
Status
Completed · report July 5, 1967
Report
Brief approved by the director
Case key
119096

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
----------------------------------------------------------------------------------------------------------------------------
2-0074   67/2/3    LACONIA,NH          CESSNA P206A        CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 35, 400
        TIME - 1100                    N2511X              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 237 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     IN FLIGHT: LOW PASS
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE,SPEED,AND ALTITUDE
           MISCELLANEOUS ACTS,CONDITIONS - UNWARRANTED LOW FLYING
        FACTOR(S)
           TERRAIN - SNOW-COVERED
        REMARKS- PLT DOES NOT REMEMBER CIRCUMSTANCES OF THE ACCIDENT. CRASH SITE ON FARM OWNED BY PLT.

Aircraft

Registration
N2511X
Reported as
Cessna P206A
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.