SEA67D0239

NTSB accident investigation · Meyers 200-A · Pomeroy, WA · February 10, 1967

Accident · Minor injuriesClosed
Date
February 10, 1967
Place
Pomeroy, WA · POMEROY, WA
Injuries
1 minor
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N34381Meyers 200-A
Status
Completed · report July 11, 1967
Report
Brief approved by the director
Case key
118925

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-0454  67/2/10    POMEROY,WASH        MEYERS 200-A        CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1630                    N34381              PX-  0  0  0  BUSINESS                  AGE 66, 3800 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            300 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           FIRE OR EXPLOSION: IN FLIGHT                             IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           MISCELLANEOUS ACTS,CONDITIONS - FIRE IN ENGINE
           MISCELLANEOUS ACTS,CONDITIONS - *ERROR-INVALID CODE*
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND

Aircraft

Registration
N34381
Reported as
Meyers 200-A
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.