FTW67D0579

NTSB accident investigation · Navion A · Mulege, Mexico · April 10, 1967

Accident · No injuriesClosed
Date
April 10, 1967
Place
Mulege, Mexico · MULEGE,MEX, MX
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N8557HNavion A
Status
Completed · report February 23, 1968
Report
Brief approved by the director
Case key
116746

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
----------------------------------------------------------------------------------------------------------------------------
6-0036  67/4/10    MULEGE,MEX          NAVION A            CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1215                    N8557H              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  AGE 53, 11024 TOTAL
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            HOURS, 1000 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - MULEGE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    TAKEOFF: RUN
           GEAR COLLAPSED                                           TAKEOFF: RUN
        REMARKS- INVESTIGATION UNDER JURISDICTION OF MEXICO GOVT.

Aircraft

Registration
N8557H
Reported as
Navion A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Mulege

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.