Incident Boeing 737-7H4 N272WN,
ASN logo
ASN Wikibase Occurrence # 163214
 
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:Sunday 12 January 2014
Time:18:10
Type:Silhouette image of generic B737 model; specific model in this crash may look slightly different    
Boeing 737-7H4
Owner/operator:Southwest Airlines
Registration: N272WN
MSN: 32527/2224
Year of manufacture:2007
Engine model:CFM INTL CFM56-7B24
Fatalities:Fatalities: 0 / Occupants: 131
Aircraft damage: None
Category:Incident
Location:M. Graham Clark Downtown Airport (KPLK), Branson, MO -   United States of America
Phase: Landing
Nature:Passenger - Scheduled
Departure airport:Chicago-Midway Airport, IL (MDW/KMDW)
Destination airport:Branson (KBBG)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
A Boeing 737-700, operating as Flight SWA4013, in apparent error, landed without incident at M. Graham Clark Downtown Airport (KPLK), Branson, Missouri.

Southwest Airlines issued the statement:

The Southwest Airlines Pilot in command of flight #4013 safely landed at (PLK) Taney County airport this evening. The Boeing 737-700 carried 124 Customers and a crew of five and was operating as a scheduled flight from Chicago Midway to Branson.

Our ground crew from the Branson airport has arrived at the airport to take care of our Customers and their baggage. The landing was uneventful, and all Customers and Crew are safe."

The flight crew briefed a plan to have radar vectors to the final approach course at Branson Airport and to use the RNAV (GPS) Runway 14 to line up on the final approach. The flight crew programmed the flight management system for the approach and set up the onboard navigation systems accordingly; including the use of distance measuring equipment from another approach navigation aid to provide additional situation awareness. During descent, the flight crew discussed the navigation information displayed, compared it to the lights they could see on the horizon, and confirmed what they believed to be the airport beacon based on that comparison early in the descent.

The approach controller cleared the flight direct to the final approach fix depicted on the RNAV approach to the runway of intended landing. While still about 20 miles from the destination airport, the approach controller advised the crew the airport was located at their 11 o'clock position and 15 miles although at the time, that position more closely approximated Downtown Airport. Branson Airport was slightly left at their 10 o'clock position and almost 20 miles. The flight crew called the airport in sight and accepted a visual approach clearance and handoff to Branson control tower. Upon checking in with Branson Tower, the crew was cleared to land on runway 14 at Branson.

When the crew identified what they believed to be Branson Airport early in the descent, they did not crosscheck or verify the airport position using onboard navigation after that point. Perceiving they were a little high on the approach into Downtown Airport, they widened the base leg for descent and then descended below approach control radar coverage as they turn onto final approach. Therefore, from the perspective of the approach controller this appeared to be a normal flight path into Branson Airport up to the point when radar contact was lost.

Instead, the flight crew lined up on final approach to runway 12 at Downtown Airport and proceeded to land. The captain recognized the error soon after touchdown when he realized the runway was shorter than expected and he applied maximum braking, coming to a stop about 300 feet from the end of the paved surface.

The National Transportation Safety Board determines the probable cause(s) of this incident as follows:
•The Flight crew's failure to properly identify the airport and runway of intended landing.

Contributing to the incident was the flight crew's failure to comply with procedures for use of navigation information and visual cues to verify the airport and runway of intended landing and the air traffic controller's issuance of erroneous airport geographic information without including the location of proximate airports.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: DCA14IA037
Status: Investigation completed
Duration:
Download report: Final report

Sources:

https://www.nbcdfw.com/news/local/Southwest-Jet-Lands-At-Wrong-Missouri-Airport-239852881.html

Re: takeoff capability, see "Greyfox", 737 ferry flight takeoff, in following thread.
https://forums.jetphotos.com/showthread.php?13871-Minimum-runway-length-(meters)-for-Boeing-737-500-700
NTSB

History of this aircraft

Other occurrences involving this aircraft
10 December 2023 N272WN Southwest Airlines 0 Saint Louis-Lambert International Airport, MO (STL) unk
Brake problem

Location

Revision history:

Date/timeContributorUpdates
13-Jan-2014 04:51 Geno Added
13-Jan-2014 12:59 bizjets101 Updated [Registration, Cn]
13-Jan-2014 14:32 northwest85 Updated [Total occupants]
28-Jan-2014 06:53 Geno Updated [Total occupants, Narrative]
05-Sep-2015 15:43 Aerossurance Updated [Source, Narrative]
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]

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