- Date
- February 20, 1966
- Place
- Wellington, KS · WELLINGTON, KS
- Injuries
- 1 minor
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N4942ZPiper PA-22
- Status
- Completed · report August 25, 1966
- Report
- Brief approved by the director
- Case key
- 172803
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-1665 66/2/20 WELLINGTON KANS PIPER PA-22 CR- 0 0 1 INSTRUCTIONAL STUDENT, AGE 44, 15 TOTAL TIME - 1030 N4942Z PX- 0 0 0 SOLO HOURS, ALL IN TYPE, NOT DAMAGE-SUBSTANTIAL OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - WELLINGTON TYPE OF ACCIDENT PHASE OF OPERATION GROUND-WATER LOOP-SWERVE LANDING: ROLL GEAR COLLAPSED LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE SKY CONDITION CEILING AT ACCIDENT SITE BROKEN 2000 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE RELATIVE BEARING OF WIND NONE RIGHT QUARTERING HEAD WIND 023-067 DEGREES TEMPERATURE-F WIND DIRECTION-DEGREES 30 70 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 17 VFR TYPE OF FLIGHT PLAN NONE
Aircraft
- Registration
- N4942Z
- Reported as
- Piper PA-22
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Wellington
N4942ZRegistration cancelled Jul 30, 2022 · Piper PA-22-108Airframe modelPiper PA-22-108Engine modelLycoming 0-235 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.