An air carrier crew running an hour and a half late failed to program the FMS with the BOS PATSS1 RNAV. After takeoff the Captain realized the error; but unable to change the departure in-flight waited for an ATC vector.

Date: 2010-11 · Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng · Phase: climb

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-clearance

Synopsis

An air carrier crew running an hour and a half late failed to program the FMS with the BOS PATSS1 RNAV. After takeoff the Captain realized the error; but unable to change the departure in-flight waited for an ATC vector.

Narrative

Departed Runway 9; very shortly after lift off Captain asked if we were supposed to be on an RNAV SID; I stated I thought we were on the Logan 4 departure; he double checked and it was the PATSS1 RNAV departure we were cleared for on the PDC clearance; he quickly tried to reprogram FMS; but the SID page is not available after takeoff; I stated we should ask for a heading immediately so we do not miss a turn. He continued to try to program in the correct fix but could not program it correctly. ATC was talking so he could not get in a word to request a heading and explain our situation. At the first break in conversation on the frequency; Controller inquired if we were on the PATSS1 RNAV departure; which we acknowledged; and then he laughed and mentioned we missed the turn at CLAAW by almost 3 miles; he then gave a heading turn to 210 degrees. Airplane came in late; loaded 15 people immediately after crew change and then agent stood over our shoulder the entire preflight prep asking if we were 'all set' multiple times; which we were not. But admittedly we rushed to help get out on time. I briefed the Logan 4 departure; and executed it. Captain caught the error immediately after takeoff before a turn or initial fix had been crossed but failed to get in the FMS programming in time. We had every intent on asking for a heading and explaining the situation before an error was made but due to frequency congestion were unable until it was too late. No traffic in the area and no conflict with other aircraft was evident or mentioned. Avoid being rushed by agents at any cost including a 25 minute turn for them! Always double check printed PDC clearance - it's the only thing that counts; instead of trying to quickly reprogram an uncooperative FMS; ask early for heading direction and admit fault before a fix is crossed and a turn is missed. We realized our mistake very early but tried to program quickly to recover before and error occurred; time and frequency congestion were not on our side; and it was too late.

Second reporter narrative

This flight was running about 1.5 hours late; so when the aircraft arrived and only 15 people to board; the gate agent was standing at the door; waiting for an 'all set' within 3-5 minutes of the flight crew arriving in the cockpit. We both felt the pressure to move faster than we should have and the First Officer quickly programmed the FMS and completed all of his duties. We were both [so busy] trying to get this flight on its way that somewhere along the line the PATSS One Departure dropped out of the FMS. Runway 9 must have been entered again or something because it was there and then right after takeoff I noticed that it was not in the FMS any longer. Because of the dark night taxi challenges; especially in BOS; I was paying close attention to my taxi route and maybe the First Officer changed something in the FMS while I was 'outside' the aircraft but I just know that things got 'busy' right as we were getting handed off to departure. I tried to re-enter the departure before we deviated from the assigned departure but the FMS will not let you do this without Lat Revving off a runway. So then I tried to manually enter the departure route; but this took too long and before I could ask for a vector from Departure he noticed that we were 3 miles late on our turn to the south and started giving us vectors instead. If ATC would not have been quite so busy I would have been able to ask for a vector before we exceeded the parameters of the departure corridor but; besides his comment about what our departure route should have been; there were no traffic conflicts; nor did he comment any further before handing us off to BOS Center. I need to be more careful about double checking the FMS before taking the runway; especially when I am not flying; because quite often the takeoff briefing is being accomplished by the First Officer while I am taxiing and am not able to take my eyes away from the 'road' as readily. I also wish there was a way for a departure to be brought up from the FMS after takeoff. I realize they are runway specific departures but once you've taken off you are unable to re-program a departure. Most importantly I need to either not let an anxious gate agent rush me; or I need to nicely ask that they wait patiently away from the cockpit so they are not 'breathing down our necks' while we are preparing the flight for a safe departure.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.