37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 320810 |
Time | |
Date | 199511 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : mco |
State Reference | FL |
Altitude | agl bound lower : 200 agl bound upper : 5000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : mco |
Operator | common carrier : air carrier |
Make Model Name | Fokker 100 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure other departure sid : sid |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | other other : other pilot : atp pilot : cfi |
Experience | flight time last 90 days : 240 flight time total : 8200 flight time type : 1100 |
ASRS Report | 320910 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | flight crew : returned to intended course or assigned course other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Departing runway 36L at mco, tower assigned us a heading on departure of 005 degrees. My first officer read this back and placed 050 degrees in the heading window and, since I was in the process of spooling up for the takeoff roll, I did not notice the problem. After takeoff, I called for 'heading select' and we started our turn. Tower called our error to our attention and we turned back to 005 degrees. This did not cause a conflict and I doubt that anything will come of it, but if an aircraft had been departing runway 35, a problem could have occurred. When departing on what is essentially runway heading, I believe that it is both unnecessary and hazardously confusing to tell a crew to place a trivial heading change into the 'game plan' while in the process of preparing for takeoff. If a heading is so important, then it should be placed in the SID.
Original NASA ASRS Text
Title: FO OF AN MLG INADVERTENTLY PUT THE WRONG HDG FOR DEP IN THE FMC CAUSING THE ACFT TO TURN TO THE WRONG HDG AFTER TKOF.
Narrative: DEPARTING RWY 36L AT MCO, TWR ASSIGNED US A HDG ON DEP OF 005 DEGS. MY FO READ THIS BACK AND PLACED 050 DEGS IN THE HDG WINDOW AND, SINCE I WAS IN THE PROCESS OF SPOOLING UP FOR THE TKOF ROLL, I DID NOT NOTICE THE PROB. AFTER TKOF, I CALLED FOR 'HDG SELECT' AND WE STARTED OUR TURN. TWR CALLED OUR ERROR TO OUR ATTN AND WE TURNED BACK TO 005 DEGS. THIS DID NOT CAUSE A CONFLICT AND I DOUBT THAT ANYTHING WILL COME OF IT, BUT IF AN ACFT HAD BEEN DEPARTING RWY 35, A PROB COULD HAVE OCCURRED. WHEN DEPARTING ON WHAT IS ESSENTIALLY RWY HDG, I BELIEVE THAT IT IS BOTH UNNECESSARY AND HAZARDOUSLY CONFUSING TO TELL A CREW TO PLACE A TRIVIAL HDG CHANGE INTO THE 'GAME PLAN' WHILE IN THE PROCESS OF PREPARING FOR TKOF. IF A HDG IS SO IMPORTANT, THEN IT SHOULD BE PLACED IN THE SID.
Data retrieved from NASA's ASRS site as of July 2007 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.