CHI77FET13

NTSB accident investigation · Starduster SA200 · Rensselaer, IN · April 3, 1977

Accident · Serious injuriesClosed
Date
April 3, 1977
Place
Rensselaer, IN · RENSSELAER, IN
Injuries
1 serious
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N6BHStarduster SA200
Status
Completed · report June 7, 1977
Report
Brief approved by the director
FAA report
19770403008439A
Case key
157509

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-0728   77/4/3    RENSSELAER,IN       STARDUSTER SA200    CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 32, 400
        TIME - 1430                    N6BH                PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 61 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - JASPER COUNTY
        DEPARTURE POINT             INTENDED DESTINATION
          RENSSELAER,IN               LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED

Aircraft

Registration
N6BH
Reported as
Starduster SA200
Category
Airplane, amateur-built
Engine
reciprocating
Damage
Destroyed
Airport
Jasper 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.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.