MD80 on RNAV SID from dfw loses associated transition waypoints when given clearance direct to nobly instead of flying charted track.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	679775
Time
Date	200512
Local Time Of Day	0601 To 1200
Place
Locale Reference	intersection : nobly
State Reference	TX
Altitude	msl single value : 29000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zfw.artcc
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other Other
Flight Phase	climbout : intermediate altitude
Route In Use	departure sid : nobly
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
ASRS Report	679775
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	679781
Events
Anomaly	aircraft equipment problem : critical non adherence : published procedure non adherence : clearance 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	Aircraft ATC Human Performance Flight Crew Human Performance Chart Or Publication Airport
Primary Problem	Ambiguous
Air Traffic Incident	Pilot Deviation

Narrative:

We were given the nobly 2 departure. Prior to departure we verified the waypoints on the clearance. After departure; we were navigating to corts. Approximately 2 mi before corts; ATC gave us a 050 heading; direct to nobly when able. We selected nobly in the FMS and proceeded to navigate direct to the waypoint. After passing nobly the #1 flight attendant called and I answered phone. At some time after that; ATC called and told us that we were 5 mi north of course. At that time I had my map scale on 40 mi and did not notice that lit was the next selected waypoint instead of cobug; ortro; then lit. We were navigating north of the SID because of the error. ATC told us to turn right 20 degrees to rejoin the departure. I manually added ortro to the FMS and we proceeded direct to rejoin. I do not know what may have caused the 2 waypoints to delete from the flight plan. It may have been a software problem. Regardless; it is our responsibility to ensure the proper waypoints are always selected.

Original NASA ASRS Text

Title: MD80 ON RNAV SID FROM DFW LOSES ASSOCIATED TRANSITION WAYPOINTS WHEN GIVEN CLRNC DIRECT TO NOBLY INSTEAD OF FLYING CHARTED TRACK.

Narrative: WE WERE GIVEN THE NOBLY 2 DEP. PRIOR TO DEP WE VERIFIED THE WAYPOINTS ON THE CLRNC. AFTER DEP; WE WERE NAVIGATING TO CORTS. APPROX 2 MI BEFORE CORTS; ATC GAVE US A 050 HEADING; DIRECT TO NOBLY WHEN ABLE. WE SELECTED NOBLY IN THE FMS AND PROCEEDED TO NAVIGATE DIRECT TO THE WAYPOINT. AFTER PASSING NOBLY THE #1 FLT ATTENDANT CALLED AND I ANSWERED PHONE. AT SOME TIME AFTER THAT; ATC CALLED AND TOLD US THAT WE WERE 5 MI N OF COURSE. AT THAT TIME I HAD MY MAP SCALE ON 40 MI AND DID NOT NOTICE THAT LIT WAS THE NEXT SELECTED WAYPOINT INSTEAD OF COBUG; ORTRO; THEN LIT. WE WERE NAVIGATING N OF THE SID BECAUSE OF THE ERROR. ATC TOLD US TO TURN R 20 DEGS TO REJOIN THE DEP. I MANUALLY ADDED ORTRO TO THE FMS AND WE PROCEEDED DIRECT TO REJOIN. I DO NOT KNOW WHAT MAY HAVE CAUSED THE 2 WAYPOINTS TO DELETE FROM THE FLT PLAN. IT MAY HAVE BEEN A SOFTWARE PROB. REGARDLESS; IT IS OUR RESPONSIBILITY TO ENSURE THE PROPER WAYPOINTS ARE ALWAYS SELECTED.

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.