NYC72DID29

NTSB accident investigation · Pitts S-1 · Crewe, VA · May 13, 1972

Accident · Minor injuriesClosed
Date
May 13, 1972
Place
Crewe, VA · CREWE, VA
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5011Pitts S-1
Status
Completed · report February 8, 1973
Report
Brief approved by the director
Case key
166212

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-1583  72/5/13    CREWE,VA            PITTS S-1           CR-  0  0  1  INSTRUCTIONAL             COMMERCIAL, AGE 45, 8414
        TIME - 1745                    N5011               PX-  0  0  0  SOLO                      TOTAL HOURS, 12 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CREWE MUNI
        DEPARTURE POINT             INTENDED DESTINATION
          FREDERICKSBURG,VA           CREWE,VA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        REMARKS- EXCESSIVE BRAKING.

Aircraft

Registration
N5011
Reported as
Pitts S-1
Category
Airplane, amateur-built
Engine
reciprocating
Damage
Substantial damage
Airport
Crewe Muni

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.