Narrative:

Prior to starting engines at ege we loaded the flight plan in the FMS; and then preceded it by the 'visual [engine out] procedure' with all the waypoints required therein. The problem arose that only the first fix; 'abcde' was in the FMS database and the remainder had to be entered using the latitude/long. Upon taxiing out and holding short of the runway a quick review of the first fix on the escape maneuver showed it to be well beyond the second and 90 NM from the field. I brought this to the attention of the PNF and he corrected it with the correct fix in latitude/long. Subsequent discussion with the check airman; as this was a 121.440 check; revealed that ATC had in fact adopted this name for a fix which was in somewhat close proximity to the company fix. It would seem that some system of verifying waypoint names between the FAA and private operators would go a long way toward avoiding this potentially hazardous situation. If we had the ability to create FAA recognized waypoints for use in the ATC system we could avoid this kind of ambiguity. Operationally; I feel it's too much to ask of the crews to have yet another procedure for verifying the waypoints against latitude/long when they exist in the database already. It would seem to be a systemic error rather then operational.

Google
 

Original NASA ASRS Text

Title: CE560 Captain discovers during taxi that a company designed visual engine out procedure from EGE; which must be entered into the FMC manually; has a waypoint name that is the same as an FAA waypoint. This is corrected by entering Lat/Long; the same as the other waypoints in the procedure which are not in the FMC data base.

Narrative: Prior to starting engines at EGE we loaded the flight plan in the FMS; and then preceded it by the 'Visual [Engine Out] Procedure' with all the waypoints required therein. The problem arose that only the first fix; 'ABCDE' was in the FMS database and the remainder had to be entered using the LAT/LONG. Upon taxiing out and holding short of the runway a quick review of the first fix on the escape maneuver showed it to be well beyond the second and 90 NM from the field. I brought this to the attention of the PNF and he corrected it with the correct fix in LAT/LONG. Subsequent discussion with the Check Airman; as this was a 121.440 check; revealed that ATC had in fact adopted this name for a fix which was in somewhat close proximity to the Company fix. It would seem that some system of verifying waypoint names between the FAA and private operators would go a long way toward avoiding this potentially hazardous situation. If we had the ability to create FAA recognized waypoints for use in the ATC system we could avoid this kind of ambiguity. Operationally; I feel it's too much to ask of the crews to have yet another procedure for verifying the waypoints against LAT/LONG when they exist in the database already. It would seem to be a systemic error rather then operational.

Data retrieved from NASA's ASRS site as of July 2013 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.