<< >> NASA ASRS Report 562150, October 2002

The track of an air carrier departure las vegas, nv, was not what the departure controller expected. The miney RNAV departure was planned.

Attributes
ACN	562150
Time
Date	200210
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : las.airport
State Reference	NV
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : l30.tracon tower : las.tower tower : mia.tower
Operator	common carrier : air carrier
Make Model Name	MD-80 Super 80
Operating Under FAR Part	Part 121
Flight Phase	climbout : initial climbout : intermediate altitude
Route In Use	departure : on vectors departure sid : miney
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	562150
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	atc equipment other atc equipment : radar other controllerb
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew other
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance Aircraft
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Inter Facility Coordination Failure

Narrative:

On departure at las, while flying the miney departure, TRACON advised we were given runway heading for departure by tower. We were then given a heading to fly. Review of clearance (no pre departure clearance avail) read 'runway heading miney departure.' after landing, we called las tower and spoke to the supervisor. He stated it happens 30-40 times a day and they are trying to gather input from pilots as to why. He said they had reviewed the tapes and said clearance delivery used other than standard phraseology and tower did not give us runway heading. Callback conversation with reporter revealed the following information: the aircraft that was flown is being upgraded to an FMS and at this point, does not have a moving map. The crews that fly it are still becoming familiar with the operation of the system and the use of RNAV routings. There was apparently a traffic separation issue with an aircraft in the departure area.

Related reports:

• DC9 crew was not given a departure turn by the tower as expe...
• An air carrier DC9-30 turned on course after takeoff. Depart...
• Mmun departure controller questions departing B767 flight cr...
• Learjet 35 flight crew failed to turn as soon as departure c...

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

Original NASA ASRS Text

Title: THE TRACK OF AN ACR DEP LAS VEGAS, NV, WAS NOT WHAT THE DEP CTLR EXPECTED. THE MINEY RNAV DEP WAS PLANNED.

Narrative: ON DEP AT LAS, WHILE FLYING THE MINEY DEP, TRACON ADVISED WE WERE GIVEN RWY HDG FOR DEP BY TWR. WE WERE THEN GIVEN A HDG TO FLY. REVIEW OF CLRNC (NO PDC AVAIL) READ 'RWY HDG MINEY DEP.' AFTER LNDG, WE CALLED LAS TWR AND SPOKE TO THE SUPVR. HE STATED IT HAPPENS 30-40 TIMES A DAY AND THEY ARE TRYING TO GATHER INPUT FROM PLTS AS TO WHY. HE SAID THEY HAD REVIEWED THE TAPES AND SAID CLRNC DELIVERY USED OTHER THAN STANDARD PHRASEOLOGY AND TWR DID NOT GIVE US RWY HDG. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE ACFT THAT WAS FLOWN IS BEING UPGRADED TO AN FMS AND AT THIS POINT, DOES NOT HAVE A MOVING MAP. THE CREWS THAT FLY IT ARE STILL BECOMING FAMILIAR WITH THE OP OF THE SYSTEM AND THE USE OF RNAV ROUTINGS. THERE WAS APPARENTLY A TFC SEPARATION ISSUE WITH AN ACFT IN THE DEP AREA.

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.