Free Republic
Browse · Search
News/Activism
Topics · Post Article

Skip to comments.

NTSB Update on Southwest Airlines Runway Incident at Midway Airport
NTSB | 12/16/05

Posted on 12/16/2005 7:20:18 AM PST by pabianice

Washington December 15, 2005 - The National Transportation Safety Board today released the following update on its investigation into the accident involving Southwest Airlines flight 1248, a Boeing 737-700 on December 8, 2005, at Midway Airport in Chicago, Illinois. The airplane overran runway 31C during the landing rollout.

The accident occurred about 7:14 pm central standard time. The airplane departed the end of the runway, rolled through a blast fence, a perimeter fence, and onto a roadway. The airplane came to a stop after impacting two automobiles. One automobile occupant was fatally injured and another seriously injured. The flight was conducted under 14 CFR Part 121 and had departed from the Baltimore/Washington International Thurgood Marshall Airport, Maryland.

The on-scene portion of the investigation has been completed. Additional fact-finding, including tests and research, will be conducted at various component manufacturers. The Safety Board staff continues to examine the information provided by the flight data recorder and the cockpit voice recorder.

Operations/Human Performance

The two pilots in the cockpit were interviewed on Saturday. Each interview took approximately three hours.

The pilots stated that everything was normal through the point of touchdown. Approaching the airport, weather was of concern to them, and they listened to the ATIS (the recorded weather update) four times during the latter portion of the flight. They stated that they agreed with the dispatcher's assessment of the conditions for landing on runway 31C and backed up that assessment by inputting the numbers into the on-board laptop computer tool.

The computer confirmed that the landing would be within the operational parameters of the airplane and Southwest's procedures, they said. Autobrakes were set on MAX, and they activated after a "firm" touchdown. The flying pilot (Captain) stated that he could not get the reverse thrust levers out of the stowed position. The first officer, after several seconds, noticed that the thrust reversers were not deployed and activated the reversers without a problem. At some point, the Captain noticed that the airplane was not decelerating normally and applied maximum braking manually. The first officer also became aware of the poor braking effectiveness, moved his seat farther forward, and also applied maximum braking. They stated that they continued to apply maximum pressure to the brakes as the airplane went straight off the end of the runway and came to a stop.

Interviews were conducted with a number of other Southwest Airlines flight crews, including the crew of the last Southwest flight to land at Midway and a subsequent crew that diverted to St. Louis.

Airplane Performance

Preliminary calculations show that the airplane touched down with about 4,500 feet of remaining runway and was on the runway for about 29 seconds. Preliminary calculations also show that, for the runway conditions and use of brakes and thrust reverser that occurred, the stopping distance without hitting obstructions would have been about 5,300 feet (the actual stopping distance was about 5,000 feet). In addition, had the airplane landing into the wind, rather than with a tail wind, the stopping distance for a landing would have been about 1,000 feet less.

Documentation of aircraft performance from the scene has been completed to the maximum extent possible. It was not possible to observe tire marks from much of the landing rollout due to the fact that the aircraft landed on a snow-covered runway and snow fell on the runway immediately following the accident.

FDR data show that autobrakes were active and provided high brake pressure upon touchdown. Autobrakes and manual braking continued to provide high brake pressure throughout the landing roll.

FDR data show that thrust reversers were activated about 18 seconds after touchdown or about 14 seconds before contact with the blast fence. Testing and examination of the thrust reverser systems will continue.

Investigators have obtained the laptop computer tool used by the accident flight crew. It will be examined and calculations of landing performance will be compared to flight manual data.

Eleven security-type video cameras were identified on the airport that may show imagery of the airplane rollout or the surface of the runway and taxiway at the time of the accident. The videos will be reviewed.

Meteorology

National Weather Service forecasters and other personnel were interviewed. An enhanced snow band was in the area producing localized heavy snow due to lake enhancement. This apparently is a somewhat unusual weather phenomenon, as the band swath was only 20 to 30 miles wide with snow accumulations of 10 inches right over Midway Airport.

Midway Airport weather observation equipment and records were examined and all equipment was working normally during the evening of the accident.

Southwest Airlines dispatchers who were associated with the accident flight were interviewed. Prior to the takeoff from Baltimore, when weather conditions deteriorated and the runway switched to runway 31C, the dispatcher determined that runway 31C was approved for landing for flight 1248. Runway conditions, braking action, wind speed and direction, airplane weight and mechanical condition of the aircraft are typical factors considered in making such decisions. The flight was contacted twice on the way to Midway and the appropriateness of using the runway for landing was reaffirmed during both contacts.

Official weather observations:

Approximately 20 minutes prior to the accident, the winds were from 100 degrees at 11 knots, visibility was mile in moderate snow and freezing fog, the ceiling was broken at 400 feet, and overcast at 1400 feet, temperature - 3C, dew point -5C, altimeter setting 30.06 in. Hg. Remarks - runway 31C rvr (runway visual range) 4500 feet, snow increment - 1 inch of new show in the last hour, 10 inches on the ground.

Approximately 23 minutes after the accident, a special observation revealed winds out of 160 degrees at 5 knots, visibility ¬ mile in heavy snow, freezing fog, sky obscured with a vertical visibility of 200 feet, temperature -4C, dewpoint -5C. Remarks - runway 31C, rvr 3000 feet.

Toxicology

Blood and urine samples were obtained from both pilots. The disposition of the blood samples is being reviewed.

Structures

The aircraft has been removed from the accident site and was transferred to a hangar at Midway Airport. The maintenance log revealed no writeups or deferred items for the accident flight or several previous flights.

Professional surveyors completed a survey of the accident scene and the geography leading up to the site to include the locations of parts shed by the aircraft after it left the paved runway surface and the blast fence destroyed during the accident sequence.

Powerplants

Both engines were visually examined at the accident site. Although the first stage compressor blades of both engines showed foreign object damage, they were all intact and present. Wood from the blast fence and other debris was present in both engines. A visual examination of the turbine sections revealed no missing blades.

The 60-day engine history revealed no deferrals or writeups. Each engine has two thrust reverser sleeves. FDR data indicated that all four sleeves were deployed until after the airplane left the paved runway overrun surface. Hydraulic system B (that runs the thrust reversers) revealed no leaks.

Systems

The Systems Group documented the switches, circuit breakers and controls in the cockpit. The leading edge slat, flap, and trailing edge flap extension measurements were taken and revealed symmetrical extension of all devices. The measurements will be compared to Boeing documentation to determine exact extension.

Chicago Fire Department personnel were interviewed to determine if any switch positions or other items were altered during the rescue effort. The Fire Department Chief stated that the only things his people did were to disconnect the battery and turn off the crew oxygen source.

The brakes were found in good condition with adequate wear remaining. The main landing gear tires had acceptable tread depth and no indication of flat spots.

Air Traffic Control

The local controller, two tower controllers, and the tower supervisor were interviewed. All controllers stated that they saw the aircraft lights during the landing roll, but did not see the actual touchdown.

The investigation has revealed that runway 31C was used as the landing runway because it contained lower landing minimums for aircraft using the ILS approach. If runway 13C was used, the runway most aligned with the wind, pilots would have been unable to land because of insufficient landing minimums.

Survival Factors/Airports

All flight attendants were interviewed. They all said that they noted a smooth landing but that the deceleration feeling thereafter seem less than usual. They noted that the emergency lighting came on after the airplane came to rest, and one flight attendant opened the L1 door to begin the evacuation. The emergency slide deployed automatically, but its angle in relation to the ground was less than ideal.

This caused passengers to begin to pile up around the bottom of the slide. Rescue personnel assisted people away from the slide. The first officer deplaned after about 5 passengers and also assisted in getting people away from the airplane.

Further factual updates will be issued when appropriate.


TOPICS: Business/Economy; Culture/Society; Government; News/Current Events; US: Illinois
KEYWORDS: flight1248; mdw; ntsb; swa
Navigation: use the links below to view more comments.
first 1-2021-28 next last

1 posted on 12/16/2005 7:20:19 AM PST by pabianice
[ Post Reply | Private Reply | View Replies]

To: pabianice
Right after the accident, I saw a woman from NTSB on TV saying (paraphrasing) "People want a quick determination, of course. But that's not how we do things. We will thoroughly study all the evidence and then perform a detailed analysis, and generate a report. This process may take a year or more."

Turns out it pretty much took a week. Seems odd to me.

2 posted on 12/16/2005 7:26:21 AM PST by ClearCase_guy
[ Post Reply | Private Reply | To 1 | View Replies]

To: pabianice

I'm not a pilot, but if I were trying to get the thrust reversers operational and they weren't going, I would be screaming bloody murder to the copilot to assist.

Brakes on snow/ice are not gonna do it.


3 posted on 12/16/2005 7:28:33 AM PST by Paloma_55 (Which part of "Common Sense" do you not understand???)
[ Post Reply | Private Reply | To 1 | View Replies]

To: pabianice
"The flying pilot (Captain) stated that he could not get the reverse thrust levers out of the stowed position. The first officer, after several seconds, noticed that the thrust reverser's were not deployed and activated the reverser's without a problem."

This seems strange that the Captain would not remark about the deployment problem with the thrust reverser's. Oh, well when the pucker factor is high (like on this approach/landing) things happen fast and furious.

Very sad about the little boy who was killed.
4 posted on 12/16/2005 7:32:28 AM PST by lowbuck (The Blue Card (US Passport). . . Don't leave home without it!)
[ Post Reply | Private Reply | To 1 | View Replies]

To: pabianice

Sounds like a bad decision to land under those marginal conditions.


5 posted on 12/16/2005 7:34:11 AM PST by EagleUSA
[ Post Reply | Private Reply | To 1 | View Replies]

To: EagleUSA

Sounds like pilot error to me.

He landed with 4500 feet left when he needed 5000+. A head wind would have dropped it to 4000, but it was a tail wind.


6 posted on 12/16/2005 7:49:46 AM PST by Lokibob (Spelling and typos are copyrighted. Please do not use.)
[ Post Reply | Private Reply | To 5 | View Replies]

To: EagleUSA

From the sound of the report they were landing WITH the wind? Any idea why that might be?


7 posted on 12/16/2005 7:56:08 AM PST by TalonDJ
[ Post Reply | Private Reply | To 5 | View Replies]

To: TalonDJ
>Any idea why that might be?

Midway couldn't use
other runways because they
would have interferred

with patterns out of
O'Hare Airport. That is what
local papers say.

8 posted on 12/16/2005 7:59:33 AM PST by theFIRMbss
[ Post Reply | Private Reply | To 7 | View Replies]

To: pabianice; All
Preliminary calculations show that the airplane touched down with about 4,500 feet of remaining runway and was on the runway for about 29 seconds. Preliminary calculations also show that, for the runway conditions and use of brakes and thrust reverser that occurred, the stopping distance without hitting obstructions would have been about 5,300 feet (the actual stopping distance was about 5,000 feet). In addition, had the airplane landing into the wind, rather than with a tail wind, the stopping distance for a landing would have been about 1,000 feet less.

I would like to hear from anyone who has flown an ILS GS into that runway if it is normal to put down in that location. Isn't that an 8000ft runway?

9 posted on 12/16/2005 8:03:49 AM PST by Pukin Dog (Sans Reproache)
[ Post Reply | Private Reply | To 1 | View Replies]

To: pabianice
FDR data show that thrust reversers were activated about 18 seconds after touchdown or about 14 seconds before contact with the blast fence. Testing and examination of the thrust reverser systems will continue.

18 seconds after touchdown.

They knew that it was a short runway and with the weather they were going to be using the whole runway.

It seems like when the pilot couldn't get the thrust reversers to work instantly he should have gotten the first officer to do so immediately, or he should have taken back off again.

It seems like the thrust reversers are always engaged within a couple seconds of touching down when I'm traveling by airplane. Eighteen seconds is a long period of time in such a situation. Pilots are supposed to be trained to react instinctively in such situations, and if the pilot screws up the first officer is there to step in.
10 posted on 12/16/2005 8:05:12 AM PST by untrained skeptic
[ Post Reply | Private Reply | To 1 | View Replies]

To: Lokibob
Part 91 GENERAL OPERATING AND FLIGHT RULES
Subpart A--General

Sec. 91.3

Responsibility and authority of the pilot in command.

(a) The pilot in command of an aircraft is directly responsible for, and is the final authority as to, the operation of that aircraft.
(b) In an in-flight emergency requiring immediate action, the pilot in command may deviate from any rule of this part to the extent required to meet that emergency.
(c) Each pilot in command who deviates from a rule under paragraph (b) of this section shall, upon the request of the Administrator, send a written report of that deviation to the Administrator.
11 posted on 12/16/2005 8:13:46 AM PST by billorites (freepo ergo sum)
[ Post Reply | Private Reply | To 6 | View Replies]

To: TalonDJ

Read the entire article, and you'll know why.


12 posted on 12/16/2005 8:19:52 AM PST by kylaka
[ Post Reply | Private Reply | To 7 | View Replies]

To: Lokibob
He landed with 4500 feet left when he needed 5000+. A head wind would have dropped it to 4000, but it was a tail wind.

Landing too far down the runway on a clear day in Burbank, Ca., was the cause of Southwest's only other accident.

13 posted on 12/16/2005 8:23:50 AM PST by sinkspur (Trust, but vilify.)
[ Post Reply | Private Reply | To 6 | View Replies]

To: TalonDJ
From the sound of the report they were landing WITH the wind? Any idea why that might be?

Sounds like they were switched to 31C because the MDA was lower on that ILS approach. It is normally a combination of things that cause an accident rather than just one mistake. I think from memory that that runway is about 8000 feet, so it would be normal to touch down on a minimums ILS approach with a MDA of 200...250 feet AGL with about 5300 feet left. Actual touchdown only left 4500 feet. This was compounded with failure to activate reverse thrusters until 18 seconds into roll out and rapidly deteriorating conditions. It is also normal(though not always a good idea) to leave a little "insurance speed in the bank" under those conditions. Years ago I had a flight instructor that told me that the four things an aviator had no use for was "runway behind you; altitude above you; fuel left in the fuel truck and ideas you hadn't thought of yet". This could fall under one or more of those items.

14 posted on 12/16/2005 8:28:41 AM PST by River_Wrangler (Nothing difficult is ever easy!)
[ Post Reply | Private Reply | To 7 | View Replies]

To: River_Wrangler
An ILS does not have an MDA, it has a DH.

That said, I suspect a demand from the dispatcher that the aircraft be landed so as not to disrupt the schedule was a key factor. I did a little flying for an airline and the pressure to meet the schedule despite marginal weather was intense.

15 posted on 12/16/2005 8:31:44 AM PST by pabianice (I guess)
[ Post Reply | Private Reply | To 14 | View Replies]

To: River_Wrangler
It is normally a combination of things that cause an accident rather than just one mistake.

Correct, and especially applicable in this case.

16 posted on 12/16/2005 8:41:34 AM PST by r9etb
[ Post Reply | Private Reply | To 14 | View Replies]

To: Pukin Dog

31C at MDW is somewhere around 6500 feet. I saw a picture that indicated a displaced threshold but I think that was a plane landing the other direction (13C).

I heard two stories on the tailwind landing--one that they were in the process of switching runways, the other (probably more accurate) was that they couldn't use 13C because it would screw up the traffic patterns at O'Hare.

Interesting that they used autobrakes. I remember reading several postings here after the crash that it was Southwest policy *not* to use autobrakes? Whatever that may be, the brakes weren't the problem.

Even if there was a mechanical problem with the reversers, the pilot landed long (apparently), so the NTSB will nail him on that at least. Sounds like if he'd hit the landing spot where he "should" have, then he would have just barely been able to stop the plane even with just the brakes, although it would have been a wild ride.

}:-)4


17 posted on 12/16/2005 8:44:03 AM PST by Moose4 (Liberals and vampires: Both like death, both hate crosses, and both are bloodsuckers.)
[ Post Reply | Private Reply | To 9 | View Replies]

To: Pukin Dog

I believe the runway landed on is 6522 feet.


18 posted on 12/16/2005 8:50:21 AM PST by tahoeblue
[ Post Reply | Private Reply | To 9 | View Replies]

To: pabianice
An ILS does not have an MDA, it has a DH.

I stand corrected. God, I hate getting old. First thing that goes is the memory.

19 posted on 12/16/2005 8:55:49 AM PST by River_Wrangler (Nothing difficult is ever easy!)
[ Post Reply | Private Reply | To 15 | View Replies]

To: Moose4
I don't know a lot about the 737, but I don't think reversers can be activivated until the engines are at idol. I seriously doubt there was anything wrong with the reversers. The Southwest autobrake policy was not about safety though.

For reasons I don't know, it is clear the pilot landed long, and not having reversers available compounded the original error. I personally dont like autobrakes, and would prefer to let reversers take me down to 80kts, then apply brakes.

Based on what we know (which aint much) I think the long landing is the original pilot error, especially if he came out of autoland at minimums. It was a -700, so the computer should have put him down in a better place.

My guess is the pilot freaked, came out of auto at minimums, and overshot.
20 posted on 12/16/2005 8:56:01 AM PST by Pukin Dog (Sans Reproache)
[ Post Reply | Private Reply | To 17 | View Replies]


Navigation: use the links below to view more comments.
first 1-2021-28 next last

Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.

Free Republic
Browse · Search
News/Activism
Topics · Post Article

FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson