MIA66D0544

NTSB accident investigation · Cessna 182 · Little River, SC · May 4, 1966

Accident · No injuriesClosed
Date
May 4, 1966
Place
Little River, SC · LITTLE RIVER, SC
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8607TCessna 182
Status
Completed · report June 15, 1966
Report
Brief approved by the director
Case key
172148

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-1000   66/5/4    LITTLE RIVER SC     CESSNA 182          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 42, 463
        TIME - 1045                    N8607T              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 45 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MCLAMB
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND

Aircraft

Registration
N8607T
Reported as
Cessna 182
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Mclamb

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.