CHI70F0063

NTSB accident investigation · Navion A · Hartford City, IN · July 3, 1969

Accident · No injuriesClosed
Date
July 3, 1969
Place
Hartford City, IN · HARTFORD CITY, IN
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N91512Navion A
Status
Completed · report August 18, 1969
Report
Brief approved by the director
Case key
167850

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-2080   69/7/3    HARTFORD CITY,IND   NAVION A            CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 54, 2500
        TIME - 1740                    N91512              PX-  0  0  3  BUSINESS                  TOTAL HOURS, 2000 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - INMAN FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        REMARKS- HEAVILY LOADED.

Aircraft

Registration
N91512
Reported as
Navion A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Inman 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.