CHI72FEG36

NTSB accident investigation · Forney F1A · Batavia, OH · May 5, 1972

Accident · No injuriesClosed
Date
May 5, 1972
Place
Batavia, OH · BATAVIA, OH
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3028GForney F1A
Status
Completed · report February 13, 1973
Report
Brief approved by the director
Case key
166012

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-1971   72/5/5    BATAVIA,OHIO        FORNEY F1A          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 41, 37 TOTAL
        TIME - 1140                    N3028G              PX-  0  0  0  SOLO                      HOURS, 12 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CLERMONT COUNTY
        DEPARTURE POINT             INTENDED DESTINATION
          PHILLIPSBURG OHIO           BATAVIA,OHIO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL

Aircraft

Registration
N3028G
Reported as
Forney F1A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Clermont County

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.

Other investigations on N3028G · 3

Matched to the same aircraft by N-number and date.