CHI67D0002

NTSB accident investigation · Luscombe 8F · Ringwood, IL · May 1, 1966

Accident · No injuriesClosed
Date
May 1, 1966
Place
Ringwood, IL · RINGWOOD, IL
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2000BLuscombe 8F
Status
Completed · report August 9, 1966
Report
Brief approved by the director
Case key
171789

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-1415   66/5/1    RINGWOOD ILL        LUSCOMBE 8F         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 39, 5200
        TIME - 1230                    N2000B              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 8 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - GALT FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT RUNWAY
        REMARKS- LANDED ON SOFT SOD RUNWAY AFTER USING PAVED RUNWAY.

Aircraft

Registration
N2000B
Reported as
Luscombe 8F
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Galt Field

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.