MIA67D0093

NTSB accident investigation · Cessna 172 · Birmingham, AL · July 28, 1966

Accident · No injuriesClosed
Date
July 28, 1966
Place
Birmingham, AL · BIRMINGHAM, AL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3823LCessna 172
Status
Completed · report September 1, 1966
Report
Brief approved by the director
Case key
121944

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-1772  66/7/28    BIRMINGHAM ALA      CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 49, 23 TOTAL
        TIME - 0930                    N3823L              PX-  0  0  0  PRACTICE                  HOURS, 5 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - BIRMINGHAM MUN.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: RUNWAY OR APPROACH LIGHTS                 LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS

Aircraft

Registration
N3823L
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Birmingham Mun.

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.