Saab-Scania Ab (Saab) SAAB 340B N420XJ

Summary

On 25 February 2004 at about 02:10 local time, a Saab-Scania Ab (Saab) SAAB 340B registered N420XJ, operated by Mesaba Aviation Inc, was involved in an accident near Romulus, Michigan, United States. 32 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

Date

25 February 2004 at 02:10

Classification

Accident

Location

Romulus, Michigan, United States

Nearest airport

Detroit Metropolitan Wayne Cou (DTW)

Coordinates

42.2122, -83.3533

Aircraft

Saab-Scania Ab (Saab) SAAB 340B

Registration

N420XJ

Category

Airplane

Engines

2

Operator

Mesaba Aviation Inc

Operating rule

Part 121: Air Carrier

Phase of flight

Not recorded

Route

Romulus → Muskegon

Aircraft damage

Substantial

Weather

VMC

Light

Night/Dark

NTSB number

CHI04LA077

Nobody was injured.

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB 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.

Quoted verbatim from the NTSB record.