# Incident 20070411006339I: Beech 1900D, Chicago, IL, April 11, 2007 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: April 11, 2007, 21:00 local time - Place: Chicago, IL - Airport: Chicago Midway - Damage: Minor damage - Phase of flight: Other Ground Ops - Operating rules: Air carrier (Part 121) - Operator: AMWA - Location: 41.7856° N, 87.7527° W: Placed by OpenAirDocs at CHICAGO MIDWAY INTL (MDW), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=41.7856&lon=-87.7527&mi=10 - Aircraft: N135YV, a cancelled registration (https://openairdocs.org/deregistered/N135YV-2010-10-05) (OpenAirDocs) - Registry model: Beech 1900D (registry code 1154162, https://openairdocs.org/model/beech-1900d) (OpenAirDocs) - Registry engine: Pratt & Whitney Canada PT6A-6 series (registry code 52150, https://openairdocs.org/engine/pratt-whitney-canada-pt6a-6-series) (OpenAirDocs) - Reported make and model: BEECH 1900D - People aboard: 11 - Fatal injuries: 0 - Pilot flight hours: 5,200 total, 2,500 in this make and model, 200 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20070411006339I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) WHILE PUSHING THE AIRCRAFT FROM THE GATE THE FLIGHT CREW PROCEEDED TO START BOTH ENGINES, WHICH THE STATION MANAGER STATED WAS AGAINST COMPANY POLICY. TO FURTHER COMPOUND THE SITUATION, THE PERSON WHO WAS PUSHING THE AIRCRAFT WAS USING AN IMPROPER TUG THAT WAS DESIGNED TO PULL BAGGAGE CARTS. HE WAS ALSO PUSHING THE AIRCRAFT USING THE BACK HITCH AS THERE WAS NO HITCH ON THE FRONT OF THE TUG. AS THE AIRCRAFT WAS BEING PUSHED BACK WITH ENGINES STARTING, THE TOW BAR APPARENTLY FAILED AND THE TUG SWUNG AROUND AND IMPACTED THE #1 PROPELLER DESTROYING IT. THE STATION MANAGER ALSO ALLEGED THAT A WING WALKER REFUSED TO PARTICIPATE BECAUSE HE FELT IT WAS AN UNSAFE PROCEDURE. THE STATION MANAGER WAS NOT ON SITE AT THE TIME OF THE INCIDENT. THE STATION MANAGER INFORMED ME THAT THE COMPANY HAD TERMINATED THE PUSHBACK DRIVER. THE AIRCRAFT WAS RETURNED TO SERVICE BY THE COMPANY AND AN FAA FORM 8020-23 WAS COMPLETED AND SENT TO THE WICHITA KANSAS FSDO FOR REFERENCE. ^PRIVACY DATA OMITTED^ ## Other reports on N135YV (6) Matched to the same aircraft by N-number and date. - [Incident 20040423007339I](https://openairdocs.org/incident/20040423007339I), Apr 23, 2004: Beech 1900D (N135YV), Farmington, NM. (-23) On April 23, 2004, at 1515 CST, a Beech BE-1900-D, N135YV, registered to mesa airlines, inc., (air midwest, flight no. 4000) declared an emergency on… - [Incident 20020829036809I](https://openairdocs.org/incident/20020829036809I), Aug 29, 2002: Beech 1900D (N135YV), Baltimore, MD. (-23) During approach, a passenger got out of his seat to ask pilot where the restroom was. Pilot told him there was none available. Passenger became… - [Incident 20020822027169I](https://openairdocs.org/incident/20020822027169I), Aug 22, 2002: Beech 1900D (N135YV), Substantial damage. (-23) On August 22, 2002, at approximately 13:30 EST time, aircraft N135YV received a lightning strike to the right engine. The crew declared an emergency and… - [Incident 20020624016639I](https://openairdocs.org/incident/20020624016639I), Jun 24, 2002: Beech 1900D (N135YV), Pittsburgh, PA. (-23) During a repositioning flight from duj to hts air midwest flight #5956, N135YV, a BE-1900-D diverted to pit due to the #1 (left) engine losing oil… - [Incident 20020614027159I](https://openairdocs.org/incident/20020614027159I), Jun 14, 2002: Beech 1900D (N135YV), Charlotte, NC, Minor damage. (-23) On taxi out crew heard and felt a thump. Crew thought initially that they had went over a pot hole or a drain on the taxi way. Crew noticed during the… - [Incident 19960928033399I](https://openairdocs.org/incident/19960928033399I), Sep 28, 1996: Beech 1900D (N135YV), Parkersburg, WV, Minor damage. Narrative: during a training flight to practice reduced visibility take-offs, the aircraft went off the right side of the runway. The instructor who sat in the… 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.