Flight crew of B737-400 experience track deviation on ferra RNAV SID/phn transition from dfw.

Attributes
ACN	700086
Time
Date	200606
Place
Locale Reference	airport : dfw.airport
State Reference	TX
Altitude	msl single value : 10000
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zfw.artcc
Operator	common carrier : air carrier
Make Model Name	B737-400
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	climbout : initial
Route In Use	departure sid : ferra2
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
ASRS Report	700086
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	700087
Events
Anomaly	aircraft equipment problem : critical non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance controller : issued advisory
Supplementary
Problem Areas	Chart Or Publication Aircraft Flight Crew Human Performance
Primary Problem	Ambiguous
Air Traffic Incident	Pilot Deviation

Narrative:

I was the PF and the captain was communicating with ATC and programming the box. We were held down by ATC for traffic. We had both checked the RNAV routing twice on the ground after a runway change and the first time discontinuities were present and we resolved them. After being given a clearance to direct ferra; we were then given clearance direct pnh. The captain noticed another discontinuity; closed it up; and inadvertently picked the next fix after ferra; which was then tbe. The two fixes after ferra had disappeared. Because we had double checked the fixes on the ground; I failed to double check the box also. We ended up encroaching into another sector without clearance. There was no traffic conflict but we nonetheless entered the sector. Whether it was a box error or pilot error is something the captain and I have discussed. Obviously it was ultimately our failure to prevent it even if it was an anomaly of the database.

Original NASA ASRS Text

Title: FLT CREW OF B737-400 EXPERIENCE TRACK DEV ON FERRA RNAV SID/PHN TRANSITION FROM DFW.

Narrative: I WAS THE PF AND THE CAPT WAS COMMUNICATING WITH ATC AND PROGRAMMING THE BOX. WE WERE HELD DOWN BY ATC FOR TFC. WE HAD BOTH CHKED THE RNAV ROUTING TWICE ON THE GND AFTER A RWY CHANGE AND THE FIRST TIME DISCONTINUITIES WERE PRESENT AND WE RESOLVED THEM. AFTER BEING GIVEN A CLRNC TO DIRECT FERRA; WE WERE THEN GIVEN CLRNC DIRECT PNH. THE CAPT NOTICED ANOTHER DISCONTINUITY; CLOSED IT UP; AND INADVERTENTLY PICKED THE NEXT FIX AFTER FERRA; WHICH WAS THEN TBE. THE TWO FIXES AFTER FERRA HAD DISAPPEARED. BECAUSE WE HAD DOUBLE CHKED THE FIXES ON THE GND; I FAILED TO DOUBLE CHK THE BOX ALSO. WE ENDED UP ENCROACHING INTO ANOTHER SECTOR WITHOUT CLRNC. THERE WAS NO TFC CONFLICT BUT WE NONETHELESS ENTERED THE SECTOR. WHETHER IT WAS A BOX ERROR OR PLT ERROR IS SOMETHING THE CAPT AND I HAVE DISCUSSED. OBVIOUSLY IT WAS ULTIMATELY OUR FAILURE TO PREVENT IT EVEN IF IT WAS AN ANOMALY OF THE DATABASE.

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.