UNK67X0146

NTSB accident investigation · Cessna 206 · Yahalica, Mexico · August 9, 1967

Accident · No injuriesClosed
Date
August 9, 1967
Place
Yahalica, Mexico · YAHALICA,MEX, MX
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N5237UCessna 206
Status
Completed · report February 27, 1968
Report
Brief approved by the director
Case key
114842

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-0083   67/8/9    YAHALICA,MEX        CESSNA 206          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 39, 1414
        TIME - 1530                    N5237U              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 374 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            IN FLIGHT: NORMAL CRUISE
           NOSE OVER/DOWN                                           LANDING: ROLL
        COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND
        REMARKS- INVESTIGATION UNDER JURISDICTION OF MEXICO GOVT.

Aircraft

Registration
N5237U
Reported as
Cessna 206
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.