- Date
- April 2, 1972
- Place
- East Hanover, NJ · EAST HANOVER, NJ
- Injuries
- 1 minor
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N2888SCessna 150G
- Status
- Completed · report January 2, 1973
- Report
- Brief approved by the director
- Case key
- 165633
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-1020 72/4/2 EAST HANOVER,NJ CESSNA 150G CR- 0 0 1 INSTRUCTIONAL STUDENT, AGE 57, 77 TOTAL TIME - 1500 N2888S PX- 0 0 0 SOLO HOURS, ALL IN TYPE, NOT DAMAGE-SUBSTANTIAL OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - HANOVER DEPARTURE POINT INTENDED DESTINATION EAST HANOVER,NJ LOCAL TYPE OF ACCIDENT PHASE OF OPERATION GROUND-WATER LOOP-SWERVE LANDING: ROLL NOSE OVER/DOWN LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT SHOULDERS WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - UNKNOWN/NOT REPORTED SKY CONDITION CEILING AT ACCIDENT SITE CLEAR UNLIMITED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE WIND DIRECTION-DEGREES NONE 315 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 10 VFR TYPE OF FLIGHT PLAN NONE REMARKS- WIND INCREASED & BECAME GUSTY.WIND GUSTING 15K.
Aircraft
- Registration
- N2888S
- Reported as
- Cessna 150G
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Hanover
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.