NYC66F0635

NTSB accident investigation · Maule M-4 · Sussex, NJ · April 25, 1966

Accident · No injuriesClosed
Date
April 25, 1966
Place
Sussex, NJ · SUSSEX, NJ
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N9827MMaule M-4
Status
Completed · report June 8, 1966
Report
Brief approved by the director
Case key
178322

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-0873  66/4/25    SUSSEX NJ           MAULE M-4           CR-  0  0  1  MISCELLANEOUS             PRIVATE, AGE 32, 221
        TIME - 1400                    N9827M              PX-  0  0  2  FERRY                     TOTAL HOURS, 11 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SUSSEX
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N9827M
Reported as
Maule M-4
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sussex

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.