<< >> NASA ASRS Report 754594, September 2007

A B737 crew reports a close-in runway change from mco runway 18R to 17L. The aircraft descended below the runway 17L FAF altitude and received a TA after an error in the FAF MCP altitude.

Attributes
ACN	754594
Time
Date	200709
Place
Locale Reference	airport : mco.airport
State Reference	FL
Altitude	msl bound lower : 2100 msl bound upper : 2500
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	tower : mco.tower
Operator	common carrier : air carrier
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 194
ASRS Report	754594
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 230
ASRS Report	754595
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : published procedure non adherence : clearance
Independent Detector	aircraft equipment : tcas other controllera other flight crewa other flight crewb
Resolutory Action	controller : issued advisory flight crew : returned to assigned altitude
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance Airport
Primary Problem	Flight Crew Human Performance

Narrative:

I was being vectored for the ILS runway 18R to mco and within 10 miles of the airport we were asked to switch to runway 17L. Approach clearance was to maintain 3000 ft until established cleared ILS runway 17L. Once established on the ILS runway 17L we mistakenly put in the FAF altitude of 1500 ft instead of 2500 ft until seedo. We descended to 2100 ft before we realized the correct altitude and started to climb back to 2500 ft. At this point we received a TA for aircraft at executive airport at minus 800 ft; and a call from mco tower to climb to 2500 ft until seedo. The rest of the approach was uneventful. We were asked to call the tower by ground control. Time was compressed; a more thorough review of charts; maybe more specific controller instructions.

Related reports:

• Controller at cle TRACON reports a false beacon target was t...
• A11 controller reports of a loss of separation between two I...
• CL300 flight crew reports TCAS RA with light aircraft during...
• A BE10 flight crew reports having taken evasive action while...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: A B737 CREW RPTS A CLOSE-IN RWY CHANGE FROM MCO RWY 18R TO 17L. THE ACFT DSNDED BELOW THE RWY 17L FAF ALT AND RECEIVED A TA AFTER AN ERROR IN THE FAF MCP ALT.

Narrative: I WAS BEING VECTORED FOR THE ILS RWY 18R TO MCO AND WITHIN 10 MILES OF THE ARPT WE WERE ASKED TO SWITCH TO RWY 17L. APCH CLRNC WAS TO MAINTAIN 3000 FT UNTIL ESTABLISHED CLRED ILS RWY 17L. ONCE ESTABLISHED ON THE ILS RWY 17L WE MISTAKENLY PUT IN THE FAF ALTITUDE OF 1500 FT INSTEAD OF 2500 FT UNTIL SEEDO. WE DSNDED TO 2100 FT BEFORE WE REALIZED THE CORRECT ALTITUDE AND STARTED TO CLB BACK TO 2500 FT. AT THIS POINT WE RECEIVED A TA FOR ACFT AT EXECUTIVE ARPT AT MINUS 800 FT; AND A CALL FROM MCO TOWER TO CLB TO 2500 FT UNTIL SEEDO. THE REST OF THE APCH WAS UNEVENTFUL. WE WERE ASKED TO CALL THE TOWER BY GND CTL. TIME WAS COMPRESSED; A MORE THOROUGH REVIEW OF CHARTS; MAYBE MORE SPECIFIC CTLR INSTRUCTIONS.

Data retrieved from NASA's ASRS site as of January 2009 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.