EMB145 crew had a track deviation in ZDC class a airspace.

Attributes
ACN	541007
Time
Date	200203
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : gve.vortac
State Reference	VA
Altitude	msl single value : 27000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zdc.artcc
Operator	common carrier : air carrier
Make Model Name	EMB ERJ 145 ER&LR
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : commercial pilot : atp
Experience	flight time last 90 days : 150 flight time total : 5500 flight time type : 1800
ASRS Report	541007
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : far non adherence : published procedure non adherence : company policies non adherence : clearance other anomaly other other spatial deviation
Independent Detector	atc equipment other atc equipment : radar other controllera
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

During flight at cruise we had a route/clearance deviation. South of gve VOR, ZDC asked what route we were flying. When I preflted the airplane, I set up the FMS route with the filed route. Once we received our clearance, we had a new route. I changed and verified (so I believe) the new route in the FMS. Both rtes were the exact same south of the gve VOR. Original filed route was ewr.biggy.J75.cae. I'm not sure of the exact cleared route, but it rejoined at gve VOR. We were flying direct from gve to cae, not on J75. The error of the incorrect route in the FMS was due to incorrect loading and reloading of the route or due to an error by the first officer who was flying and operating the FMS. We were cleared direct to gve VOR and on course. Instead of selecting the direct function on the FMS, the first officer deleted each waypoint in between and may have made a mistake, but he doesn't believe so. Regardless of the method in which the FMS was incorrectly set, there was a lack of route verification while in flight. After using FMS/FMC for several yrs, it is easy to become complacent and believe that the 'box' is correct.

Original NASA ASRS Text

Title: EMB145 CREW HAD A TRACK DEV IN ZDC CLASS A AIRSPACE.

Narrative: DURING FLT AT CRUISE WE HAD A RTE/CLRNC DEV. S OF GVE VOR, ZDC ASKED WHAT RTE WE WERE FLYING. WHEN I PREFLTED THE AIRPLANE, I SET UP THE FMS RTE WITH THE FILED RTE. ONCE WE RECEIVED OUR CLRNC, WE HAD A NEW RTE. I CHANGED AND VERIFIED (SO I BELIEVE) THE NEW RTE IN THE FMS. BOTH RTES WERE THE EXACT SAME S OF THE GVE VOR. ORIGINAL FILED RTE WAS EWR.BIGGY.J75.CAE. I'M NOT SURE OF THE EXACT CLRED RTE, BUT IT REJOINED AT GVE VOR. WE WERE FLYING DIRECT FROM GVE TO CAE, NOT ON J75. THE ERROR OF THE INCORRECT RTE IN THE FMS WAS DUE TO INCORRECT LOADING AND RELOADING OF THE RTE OR DUE TO AN ERROR BY THE FO WHO WAS FLYING AND OPERATING THE FMS. WE WERE CLRED DIRECT TO GVE VOR AND ON COURSE. INSTEAD OF SELECTING THE DIRECT FUNCTION ON THE FMS, THE FO DELETED EACH WAYPOINT IN BTWN AND MAY HAVE MADE A MISTAKE, BUT HE DOESN'T BELIEVE SO. REGARDLESS OF THE METHOD IN WHICH THE FMS WAS INCORRECTLY SET, THERE WAS A LACK OF RTE VERIFICATION WHILE IN FLT. AFTER USING FMS/FMC FOR SEVERAL YRS, IT IS EASY TO BECOME COMPLACENT AND BELIEVE THAT THE 'BOX' IS CORRECT.

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.