# Accident 19980514016179A: Enstrm F28F, Chicago/West Ch, IL, May 14, 1998 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: May 14, 1998, 15:35 local time - Place: Chicago/West Ch, IL - Airport: Dupage - Damage: Substantial damage - Phase of flight: Touch And Go Landing - Operating rules: General operating rules (Part 91) - Location: 41.8795° N, 88.2198° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=41.8795&lon=-88.2198&mi=10 - Aircraft: N86238, registered now (https://openairdocs.org/aircraft/N86238) (OpenAirDocs) - Registry model: Enstrom F-28F (registry code 3300412, https://openairdocs.org/model/enstrom-f-28f) (OpenAirDocs) - Registry engine: Lycoming HIO-360 series (registry code 41524, https://openairdocs.org/engine/lycoming-hio-360-series) (OpenAirDocs) - Reported make and model: ENSTRM F28F - People aboard: 1 - Fatal injuries: 0 - Pilot certificates: Student - Pilot flight hours: 45 total, 45 in this make and model, 23 in the last 90 days - NTSB investigation: [NTSB CHI98LA166](https://openairdocs.org/ntsb/CHI98LA166) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/19980514016179A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. MADE HARD DOWNWIND LANDING. (.4)THE HELICOPTER WAS SUBSTANTIALLY DAMAGED DURING A HARD LANDING AND SUBSEQUENT ROLL OVER DURING A POSITIONING FLIGHT AT THE DUPAGE AIRPORT. THE SOLO STUDENT WAS PRACTICING TOUCH-AND-GOES ON RUNWAY 19L WHEN HE ASKED FOR CLEARANCE TO A FIXED BASE OPERATOR NEAR RUNWAY 33. REPORTED WEATHER, TAKEN AFTER THE ACCIDENT, RECORDED THE WINDS FROM 140 AT 9 KNOTS. THE PILOT STATED 'AS I STARTED TO LAND, I KNOW I HAD GOTTEN MYSELF IN A BAD SITUATION WHEN I REALIZED MY RATE OF DESCENT WAS JUST OVER 500 FPM WITH SLOW FORWARD AIRSPEED.' (-23) THE FOLLOWING IS THE OFFICIAL FILE SUMMARY FOR THE ACCIDENT INVOLVINGN86238, ENSTROM HELICOPTER, OWNED BY OLIVER HELICOPTERS. AT THE TIME OF THE ACCIDENT THE HELICOPTER WAS BEING OPERATED UNDER 14 CFR PART 91, FLIGHT INSTRUCTION. THE PILOT OF THE N86238 WAS A STUDENT PILOT: GUS R. WARREN, RESIDING AT ^PRIVACY DATA OMITTED^ THIS FLIGHT WAS AN UNSUPERVISED SOLO TRAINING FLIGHT FROM OLIVERS HELIPORT (IS92) TO DUPAGE AIRPORT FOR NORMAL TAKE-OFF AND LANDINGS. AT APPROXIMATELY 1300 HOURS LOCAL TIME, WARREN DEPARTED IS92 TO DPA AIRPORT FOR UNSUPERVISED SOLO PRACTICE. UPON ARRIVING AT DPA AT APPROXIMATELY 1313 HOURS, MULTIPLE LANDING AND TAKEOFFS WERE MADE UNTIL 1541 HOURS. WHILE ON RUNWAY 19L, THE PILOT IDENTIFIED HIMSELF AS A STUDENT PILOT AND REQUESTED TO FLY TO THE PILOT SHOP NEXT TO JA AVIATION. TOWER GAVE A CLEARANCE TO DEPART 19L AND CLEARED TO LAND RWY 33. THE PILOT COMPLIED WITH THE CLEARANCE. ON SHORT FINAL TO RUNWAY 33, THE PILOT EXPERIENCED AN UNSTABLE FLIGHT CONDITION AT APPROXIMATELY 200 FEET. THE HELICOPTER ENTERED SETTLING WITH POWER, CONTACTING THE GROUND IN A NEAR VERTICAL DESCENT AND WITH AN UNCONTROLLED LATERAL DRIFT. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB CHI98LA166](https://openairdocs.org/ntsb/CHI98LA166), May 14, 1998: Enstrom F28 (N86238), West Chicago, IL, substantial damage. Probable cause: the student pilot attempting a tailwind landing and improper compensation for the wind resulting in too high of a sink rate and the hard landing. ## Other reports on N86238 (1) Matched to the same aircraft by N-number and date. - [Accident 20030405011399A](https://openairdocs.org/incident/20030405011399A), Apr 5, 2003: Enstrm F28F (N86238), Monroe, LA, Substantial damage. (-23) The student helicopter pilot was on a local solo flight when he lost control of the aircraft while practicing hovering. The pilot stated that he lost… From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.