- Date
- January 24, 1967
- Place
- Hagerstown, MD · HAGERSTOWN, MD
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N8098SCessna 150
- Status
- Completed · report June 16, 1967
- Report
- Brief approved by the director
- Case key
- 119338
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-0229 67/1/24 HAGERSTOWN,MD CESSNA 150 CR- 0 0 1 INSTRUCTIONAL STUDENT, AGE 22, 45 TOTAL TIME - 1400 N8098S PX- 0 0 0 TRAINING HOURS, ALL IN TYPE, NOT DAMAGE-SUBSTANTIAL OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - HAGERSTOWN MUNI TYPE OF ACCIDENT PHASE OF OPERATION GROUND-WATER LOOP-SWERVE LANDING: ROLL GEAR COLLAPSED LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 5000 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE RELATIVE BEARING OF WIND NONE LEFT CROSS WIND 248-292 DEGREES TEMPERATURE-F WIND DIRECTION-DEGREES 60 200 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 20 VFR TYPE OF FLIGHT PLAN NONE REMARKS- LEFT CROSSWIND 70 DEGREES 20 KTS.
Aircraft
- Registration
- N8098S
- Reported as
- Cessna 150
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Hagerstown Muni
N8098SRegistration cancelled Mar 1, 2006 · Cessna 150FAirframe modelCessna 150FEngine modelContinental 0-200 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.