Narrative:

I was acting as sic and pilot not flying on this flight from teb. Our assigned route was teb ruudy four lanna J48... After entering the flight plan into our FMS I expressed concern that we were unable to view the ruudy four departure procedure waypoints in the FMS even though we had selected the ruudy four departure procedure when the unit prompted us. For a backup and great situational awareness in case the FMS malfunctions during the initial climb; I manually entered the ruudy four waypoints into an aviation program foreflight on an ipad. With an external GPS; I am able to view the aircraft's position in real time on a map. After departure; the captain began to execute the ruudy four departure procedure. Upon reaching tasca and climbing through about 3;000 MSL; I noticed on the FMS the current waypoints in progress was runway 24-lanna. This was not correct; the FMS had dropped the departure procedure and had the flight director tracking a course from the runway to lanna which was further southwest on our route. Meanwhile; I am watching our aircraft's position parallel and drift further south and southeast of our required course on my ipad. I encouraged the captain to fly heading 280 for a longer period of time to prevent drifting and reach ruudy before turning southwest to lanna; but he was confused and continued to fly about a 240 degree heading towards lanna. During this time; new york center asks to state our heading and if we were flying the ruudy four. ATC then issues us a heading of 280 to fly and begins questioning what procedure we were flying and when I have time; to study the ruudy four. I responded appropriately to fly heading 280 and confirmed we were flying the ruudy four. To prevent this from occurring again; I will ensure the FMS is functioning properly and will be more firm and urgent with the PIC regarding the aircraft's position and route of flight.

Google
 

Original NASA ASRS Text

Title: CE650 First Officer reports a track deviation during the RUUDY 4 departure from TEB. The FMC did not appear correct prior to departure and was steering the aircraft to LANNA after TASCA. ATC commented and corrected the course.

Narrative: I was acting as SIC and pilot not flying on this flight from TEB. Our assigned route was TEB RUUDY FOUR LANNA J48... After entering the flight plan into our FMS I expressed concern that we were unable to view the RUUDY FOUR departure procedure waypoints in the FMS even though we had selected the RUUDY FOUR departure procedure when the unit prompted us. For a backup and great situational awareness in case the FMS malfunctions during the initial climb; I manually entered the RUUDY FOUR waypoints into an aviation program Foreflight on an iPad. With an external GPS; I am able to view the aircraft's position in real time on a map. After departure; the Captain began to execute the RUUDY FOUR departure procedure. Upon reaching TASCA and climbing through about 3;000 MSL; I noticed on the FMS the current waypoints in progress was Runway 24-LANNA. This was not correct; the FMS had dropped the departure procedure and had the flight director tracking a course from the runway to LANNA which was further southwest on our route. Meanwhile; I am watching our aircraft's position parallel and drift further south and southeast of our required course on my iPAD. I encouraged the Captain to fly heading 280 for a longer period of time to prevent drifting and reach RUUDY before turning southwest to LANNA; but he was confused and continued to fly about a 240 degree heading towards LANNA. During this time; New York Center asks to state our heading and if we were flying the RUUDY FOUR. ATC then issues us a heading of 280 to fly and begins questioning what procedure we were flying and when I have time; to study the RUUDY FOUR. I responded appropriately to fly heading 280 and confirmed we were flying the RUUDY FOUR. To prevent this from occurring again; I will ensure the FMS is functioning properly and will be more firm and urgent with the PIC regarding the aircraft's position and route of flight.

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.