An MD80 crew on the dfw SOLDO2.soldo was flying direct mei because the intervening waypoints were not in the FMS flight plan. ATC redirected en route.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	685133
Time
Date	200601
Local Time Of Day	1801 To 2400
Place
Locale Reference	navaid : uim.vor
State Reference	TX
Altitude	msl single value : 33000
Environment
Flight Conditions	Mixed
Light	Night
Aircraft 1
Controlling Facilities	artcc : zfw.artcc
Operator	common carrier : air carrier
Make Model Name	MD-88
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : takeoff climbout : initial
Route In Use	departure sid : soldo
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 10000 flight time type : 4000
ASRS Report	685133
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	aircraft equipment problem : less severe non adherence : published procedure non adherence : clearance non adherence : far other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance controller : issued advisory
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Aircraft Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On the RNAV departure from dfw (SOLDO2) aircraft was off course due to FMS loading. FMS did not have the quitman NAVAID loaded nor the el dorado fix loaded and was proceeding to 'mei' directly. ATC called and said; 'air carrier X; you're off course;' and questioned our heading and what RNAV procedure we were following. I; PNF; looked at the RNAV departure and noted that uim and eld were not in the FMS and mei was. Thus; we loaded the uim in the FMS; but by that time; ATC gave us vectors to eld; and then fly direct to eld. No TCAS advisory or conflict was caused. No problems and flight continued to destination. The loading of the SOLDO2 departure (RNAV) and the meridian (mei) transition was loaded in the FMS on the preflight. The 'box' did not have the waypoint uim or loaded and this caused the problem. Diligence in cross checking your partner's work and a 2.5 hour delay (fatigue) contributed to this deviation. Somehow the transition did not have the 2 waypoints in it but should have been caught in a cross checking environment.

Original NASA ASRS Text

Title: AN MD80 CREW ON THE DFW SOLDO2.SOLDO WAS FLYING DIRECT MEI BECAUSE THE INTERVENING WAYPOINTS WERE NOT IN THE FMS FLT PLAN. ATC REDIRECTED ENRTE.

Narrative: ON THE RNAV DEP FROM DFW (SOLDO2) ACFT WAS OFF COURSE DUE TO FMS LOADING. FMS DID NOT HAVE THE QUITMAN NAVAID LOADED NOR THE EL DORADO FIX LOADED AND WAS PROCEEDING TO 'MEI' DIRECTLY. ATC CALLED AND SAID; 'ACR X; YOU'RE OFF COURSE;' AND QUESTIONED OUR HDG AND WHAT RNAV PROC WE WERE FOLLOWING. I; PNF; LOOKED AT THE RNAV DEP AND NOTED THAT UIM AND ELD WERE NOT IN THE FMS AND MEI WAS. THUS; WE LOADED THE UIM IN THE FMS; BUT BY THAT TIME; ATC GAVE US VECTORS TO ELD; AND THEN FLY DIRECT TO ELD. NO TCAS ADVISORY OR CONFLICT WAS CAUSED. NO PROBLEMS AND FLT CONTINUED TO DEST. THE LOADING OF THE SOLDO2 DEP (RNAV) AND THE MERIDIAN (MEI) TRANSITION WAS LOADED IN THE FMS ON THE PREFLT. THE 'BOX' DID NOT HAVE THE WAYPOINT UIM OR LOADED AND THIS CAUSED THE PROBLEM. DILIGENCE IN CROSS CHKING YOUR PARTNER'S WORK AND A 2.5 HOUR DELAY (FATIGUE) CONTRIBUTED TO THIS DEV. SOMEHOW THE TRANSITION DID NOT HAVE THE 2 WAYPOINTS IN IT BUT SHOULD HAVE BEEN CAUGHT IN A CROSS CHKING ENVIRONMENT.

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.