A beechjet flight crew was unable to accept the 'ruudy two RNAV SID; white' out of teb because the a...

Narrative:

Being aware of current issues associated with the RUUDY2 departure; I briefed my sic that since we were filed for white that we should expect elvae and that we would likely need to verify what they wanted after elvae. The plate says over white to expect elvae / col / white. As we were having this discussion my sic typed elvae into the FMS which gave a message 'not in database.' we verified the spelling for elvae several times and re-entered with the same result; 'not in database.' we also verified the current database; which was loaded. I believe it was the pre departure clearance that stated if unable to comply with the RUUDY2 to advise; so we advised we did not have elvae in our database and they assigned us the TEB6. We programmed this and the flight was flown without incident. I am now aware that the collins 6000 series avionics does not appear to have elvae loaded either. The intent of this report is to point out the lack of elvae in the database; as it will likely lead to unnecessary confusion and potential course deviations for crews departing teb. The company should make crews aware that elvae is not in the database.

Original NASA ASRS Text

Title: A Beechjet Flight Crew was unable to accept the 'RUUDY TWO RNAV SID; WHITE' out of TEB because the aircraft database did not include the waypoint ELVAE; which is part of the 'WHITE' routing.

Narrative: Being aware of current issues associated with the RUUDY2 departure; I briefed my SIC that since we were filed for WHITE that we should expect ELVAE and that we would likely need to verify what they wanted after ELVAE. The plate says over WHITE to expect ELVAE / COL / WHITE. As we were having this discussion my SIC typed ELVAE into the FMS which gave a message 'Not in Database.' We verified the spelling for ELVAE several times and re-entered with the same result; 'Not in Database.' We also verified the current database; which was loaded. I believe it was the PDC that stated if unable to comply with the RUUDY2 to advise; so we advised we did not have ELVAE in our database and they assigned us the TEB6. We programmed this and the flight was flown without incident. I am now aware that the Collins 6000 series avionics does not appear to have ELVAE loaded either. The intent of this report is to point out the lack of ELVAE in the database; as it will likely lead to unnecessary confusion and potential course deviations for crews departing TEB. The company should make crews aware that ELVAE is not in the database.

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

Attributes
ACN	892429
Time
Date	201006
Local Time Of Day	1201-1800
Place
Locale Reference	TEB.Airport
State Reference	NJ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Beechjet 400
Operating Under FAR Part	Part 135
Flight Phase	Parked
Flight Plan	IFR
Component
Aircraft Component	Navigation Database
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe

A beechjet flight crew was unable to accept the 'ruudy two RNAV SID; white' out of teb because the aircraft database did not include the waypoint elvae; which is part of the 'white' routing.