- Date
- December 3, 1966
- Place
- Kingsville, TX · KINGSVILLE, TX
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N6135DPiper PA-22
- Status
- Completed · report March 30, 1967
- Report
- Brief approved by the director
- Case key
- 201147
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-4067 66/12/3 KINGSVILLE TEX PIPER PA-22 CR- 0 0 2 INSTRUCTIONAL COMMERCIAL, FL.INSTR., TIME - 0935 N6135D PX- 0 0 0 DUAL AGE 67, 10000 TOTAL DAMAGE-SUBSTANTIAL OT- 0 0 0 HOURS, 200 IN TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - KLEBERG COUNTY TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB GEAR COLLAPSED LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) MISCELLANEOUS ACTS,CONDITIONS - WATER IN FUEL PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PERSONNEL - AIRPORT SUPERVISORY PERSONNEL: IMPROPER INSPECTION OF FACILITIES FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE TERRAIN - ROUGH/UNEVEN COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- ARPT.FUEL SYSTEM WATER CONTAMINATED WHEN N6135D LAST REFUELED. ACFT TANKS WERE NOT DRAINED ADEQTLY
Aircraft
- Registration
- N6135D
- Reported as
- Piper PA-22
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Kleberg County
N6135DRegistered now · 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.