MIA67F0272

NTSB accident investigation · Cessna 150 · Icksburg, MS · November 10, 1966

Accident · No injuriesClosed
Date
November 10, 1966
Place
Icksburg, MS · ICKSBURG, MS
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7044FCessna 150
Status
Completed · report February 1, 1967
Report
Brief approved by the director
Case key
120204

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-3616  66/11/10   ICKSBURG MISS       CESSNA 150          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 23, 27 TOTAL
        TIME - 1030                    N7044F              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - VICKSBURG MUNI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF FLIGHT CONTROLS
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT SHOULDERS

Aircraft

Registration
N7044F
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Vicksburg Muni

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.