- Date
- February 10, 1967
- Place
- Hankamer, TX · HANKAMER, TX
- Injuries
- 4 fatal
- Damage
- Destroyed
- Phase of flight
- Uncontrolled descent
- Aircraft
- N4464APiper PA-22
- Status
- Completed · report June 19, 1967
- Report
- Brief approved by the director
- Case key
- 119083
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 ---------------------------------------------------------------------------------------------------------------------------- 2-0055 67/2/10 HANKAMER,TEX PIPER PA-22 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 35, 680 TIME - 2145 N4464A PX- 3 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 165 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - GULF STATE STRIP TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: UNCONTROLLED IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - SPATIAL DISORIENTATION FACTOR(S) WEATHER - FOG WEATHER BRIEFING - UNKNOWN/NOT REPORTED MISSING AIRCRAFT - LATER RECOVERED SKY CONDITION CEILING AT ACCIDENT SITE PARTIAL OBSCURATION 0 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1/4 MILE OR LESS NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F FOG 62 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE FIRE AFTER IMPACT REMARKS- RECOVERY DATE-02/15/67.
Aircraft
- Registration
- N4464A
- Reported as
- Piper PA-22
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Gulf State Strip
N4464ARegistration cancelled Oct 22, 1970 · Piper PA-22-150Airframe modelPiper PA-22-150Engine modelLycoming 0-320 series
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.