<< >> NASA ASRS Report 582821, May 2003

Heading and track deviation by a B737-300 flight crew when they misinterpret the pre departure clearance revised segment related to their IDALE2 oal SID out of las, nv.

Attributes
ACN	582821
Time
Date	200305
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	intersection : idale
State Reference	NV
Altitude	msl single value : 16000
Environment
Flight Conditions	VMC
Aircraft 1
Controlling Facilities	tracon : l30.tracon
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : intermediate altitude
Route In Use	departure sid : idale
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	582821
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : clearance non adherence : published procedure other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued advisory controller : issued new clearance flight crew : returned to intended or assigned course
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Company Chart Or Publication ATC Human Performance Flight Crew Human Performance
Primary Problem	Chart Or Publication
Air Traffic Incident	Pilot Deviation

Narrative:

Pre departure clearance was las IDALE2 oal MOD2 sfo, with a revised segment, IDALE2 bikkr oak. The SID reads for our runway 25R 'climb via 255 degree course to lodzy, then left turn direct to idale. Thence via transition or assigned route. So we flew the SID as depicted to idale then went direct to bikkr. Was asked shortly after where we were going, we said bikkr. ATC cleared us direct to shead then bikkr then oal. Rest of flight was uneventful. Both the copilot and myself discussed the original departure as well as the revised segment before pushback. If there had been no revised segment listed there would have been no problem, but as it was listed there was confusion about it only after ATC queried us. We thought we had programmed and interpreted the pre departure clearance correctly. There should be a better way to format the pre departure clearance so no confusion exists.

Related reports:

• After their crj-200 aircraft had departed; two aircraft main...
• B737NG flight crew misinterpret pre departure clearance rout...
• Air carrier flight crew taxiing wide-body aircraft mis-inter...
• Flight crew of B752 on hyper STAR to iad misinterpret cleara...
• Flight crew of A320 misinterpret MEL and weight and balance ...
• C560 crew misinterpret taxi clearance to runway 23 at cak to...

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

Original NASA ASRS Text

Title: HEADING AND TRACK DEV BY A B737-300 FLT CREW WHEN THEY MISINTERPRET THE PDC REVISED SEGMENT RELATED TO THEIR IDALE2 OAL SID OUT OF LAS, NV.

Narrative: PDC WAS LAS IDALE2 OAL MOD2 SFO, WITH A REVISED SEGMENT, IDALE2 BIKKR OAK. THE SID READS FOR OUR RWY 25R 'CLB VIA 255 DEG COURSE TO LODZY, THEN L TURN DIRECT TO IDALE. THENCE VIA TRANSITION OR ASSIGNED RTE. SO WE FLEW THE SID AS DEPICTED TO IDALE THEN WENT DIRECT TO BIKKR. WAS ASKED SHORTLY AFTER WHERE WE WERE GOING, WE SAID BIKKR. ATC CLRED US DIRECT TO SHEAD THEN BIKKR THEN OAL. REST OF FLT WAS UNEVENTFUL. BOTH THE COPLT AND MYSELF DISCUSSED THE ORIGINAL DEP AS WELL AS THE REVISED SEGMENT BEFORE PUSHBACK. IF THERE HAD BEEN NO REVISED SEGMENT LISTED THERE WOULD HAVE BEEN NO PROB, BUT AS IT WAS LISTED THERE WAS CONFUSION ABOUT IT ONLY AFTER ATC QUERIED US. WE THOUGHT WE HAD PROGRAMMED AND INTERPED THE PDC CORRECTLY. THERE SHOULD BE A BETTER WAY TO FORMAT THE PDC SO NO CONFUSION EXISTS.

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.