Accident Saab 340B N420XJ,
ASN logo
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Tuesday 24 February 2004
Time:22:10 LT
Type:Silhouette image of generic SF34 model; specific model in this crash may look slightly different    
Saab 340B
Owner/operator:Mesaba Airlines
Registration: N420XJ
MSN: 340B-420
Total airframe hrs:16158 hours
Engine model:General Electric CT7-9B
Fatalities:Fatalities: 0 / Occupants: 32
Aircraft damage: Substantial
Category:Accident
Location:Detroit-Metropolitan Wayne County Airport, MI (DTW/KDTW) -   United States of America
Phase: Unknown
Nature:Passenger - Scheduled
Departure airport:Detroit-Metropolitan Wayne County Airport, MI (DTW/KDTW)
Destination airport:Muskegon Airport, MI (MKG/KMKG)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The scheduled domestic passenger flight was being pushed back for taxi when it struck an unoccupied airplane that was parked on the ramp. Both airplanes sustained substantial damage. The 2 flight crewmembers, 1 cabin crewmember, and 29 passengers were uninjured. Dark night visual meteorological conditions prevailed at the time of the accident. The Push Tug Operator stated, "In pushing back this plane I was attempting to do it as I was trained, that is, to [prop] the front wheels on the painted line. I [normally] work on the east side and there is a line [used] for the front wheels. I had not done [a] push back [on] the west side before. While pushing this plane back I started looking for the line as I approached the line my wing walker had stopped walking the [wing] and was off to my left and slightly behind me she says she gave me a stop [signal], but due to her position I could not see her. She ran up to me and told me to stop but it was already [too] late." Excerpts from the airline's Station Operations Manual stated, "The Pushback Operator and the Captain have the overall responsibility for the safe conduct of the pushback operation. ... The Pushback Operator shall remain alert for signals given by the Wing Walker(s). When Wing Walker(s) is/are used, if visual contact between the Pushback Operator and Wing Walker is lost, stop the pushback. The Pushback Operator must continuously scan for signals and hazards. ... Before pushback of an aircraft, the Pushback Operator shall : 1. Determine where the aircraft is to be pushed back to, positioned and route to be taken. 2. Note ALL potential clearance problems to be avoided. ... 5. Review with the Captain the route to be taken. ... During pushback of an aircraft, the Pushback Operator shall: 17. Pushback ONLY when clearance from obstructions (and visual contact with Wing Walker(s), when used) is maintained. ... PUSHBACK OPERATOR CHECKLIST, BEFORE PUSHBACK CHECK 1. ASSESS ROUTE, CLEARANCES AND RAMP CONDITIONS." The Push Tug Operator tested positive for cocaine metabolite. 14 CFR Part 121 Appendix I stated, "Each person who performs a safety-sensitive function directly or by contract for an employer must be tested pursuant to an FAA-approved antidrug program conducted in accordance with this appendix." The Push Tug Operator was not on the FAA's safety-sensitive list. An airline representative reported that the airline's policy is to accomplish a pre-employment drug test for all safety-sensitive and non safety-sensitive employees. The Push Tug Operator's pre-employment drug test was reported as negative. The airline had a drug policy and an employee assistance program in-place at the time of the accident. An airline representative reported that the supervisor and coordinator for the accident gate area were two gates away and did not directly observe the accident pushback. Subsequent to the accident, the airline established a policy of random drug testing for all employees as a condition of employment.

Probable Cause: The visual lookout not maintained and the procedures not followed by the Push Tug Operator during the pushback. Factors were the parked airplane, the dark night, and the inadequate surveillance of the pushback by airline management.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: CHI04LA077
Status: Investigation completed
Duration: 1 year and 3 months
Download report: Final report

Sources:

NTSB CHI04LA077

Revision history:

Date/timeContributorUpdates
12-Oct-2022 15:00 ASN Update Bot Added

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org