A90 Controller described wrong SID routing event when air carrier flew other than assigned SID; secondary pilot report indicated PDC clearance was misread and incorrect SID was entered into FMS.

2010-02 · NASA ASRS report 875571

Date: 2010-02 · Aircraft: A319 · Phase: climb

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

Synopsis

A90 Controller described wrong SID routing event when air carrier flew other than assigned SID; secondary pilot report indicated PDC clearance was misread and incorrect SID was entered into FMS.

Narrative

Air Carrier Y departed Runway 4R on LOGAN4 SID flight planned to go to LUCOS intersection. Air Carrier X departed Runway 9 on PATTS1 SID. When Air Carrier Y was approximately 12 NM northeast of BOS; the Pilot was assigned a heading of 130 to parallel the second portion of the PATTS1 SID. Apparently realizing that Air Carrier Y was turning toward them; the Pilot of Air Carrier X stated that they were still on 'runway heading'. Air Carrier X was immediately assigned a right turn to heading 220 to maintain separation. Air Carrier X was then asked to verify the assignment of the PATTS1 SID. Strip marking indicated the PATTS1 SID assignment. After a moment the Pilot confirmed that they had been assigned the correct procedure. The Pilot also asked if separation had been lost between the 2 aircraft. This incident was then reported to the FLM (Front Line Manager) on duty. Recommendation; most pilots from BOS are receiving their IFR Clearances via PDC. They are only required to read back their 'Call Sign and transponder code' to Tower personnel; 'unless they have a question'. Since BOS now has 8 different SIDs; this submitter believes that: 1. Pilots should be required to read back; Call Sign; Assigned SID; and Transponder Code to Clearance Delivery. 2. Local Control phraseology should be changed to -- Air Carrier X; fly the PATTS1 departure; Runway Nine cleared for takeoff. 3. Pilot initial check in with Departure Control should include: Call Sign; SID; and altitudes.

Second reporter narrative

Departed Runway 9 on LOGAN 4 departure; runway heading; expect vectors. Climbing out of 8000 ft and still on runway heading; we asked Departure for a turn; since we figured he had forgotten us as we usually get a turn to the South sooner. Departure said he showed us on the PATTS ONE departure. We had briefed and were flying the Logan 4. We checked the PDC and then noticed the PATTS ONE departure listed at the bottom of the page. Departure then gave us a right turn to 220 degrees; then a turn to 270 degrees. We asked if there was a loss of separation or any problems; and we were told no. We continued as normal. After looking at the PATTS ONE SID and comparing it to what we were flying; we were on course of the first leg for the PATTS ONE SID; and when we called for the turn we were over the first turning point. Cause; I entered the route from the flight release approximately 45 minutes before departure. On the previous flight out of BOS on the same day; the same runway; we received the Logan 4 Departure; so I entered that runway and SID as well. The Logan 4 off of Runway 9 calls for runway heading; expect vectors to NELIE intersection. When I got the clearance via PDC approximately 20 minutes later; the route section showed KBOS NELIE CMK J75 DUEYS....; which is the route I had previously entered. What I did not notice was that listed below the route was PATTS ONE DEPARTURE DEDHM TRANSISTION; and neither did the Captain. It was not entered into the FMS. Why this happened: 1.) This was the last leg of the trip after a REDUCED rest overnight; and 5 days in a row for me. I was tired. Several approaches to minimums with high winds and turbulence contributed to a fatiguing day. 2.) I was EXPECTING the LOGAN FOUR departure since we had previously received that clearance earlier in the day. 3.) The SID was listed on the PDC clearance AFTER the route at the bottom of the page. After checking the PDC route against the FMS route; I was satisfied. However; I missed the SID at the bottom. I was tired; I wasn't expecting it; and it was in a poor location. Suggestions; 1.) A lot of discussion has been going on concerning the PDC clearance format. It is very simple; there should only be ONE route on the PDC; and that is the cleared route; given in the order to be flown....i.e. SID; ROUTE; STAR. If there is only one route; only one route will be entered! Please get rid of filed route and cleared route.....do not put SID's AFTER the filed route! 2.) When you are tired; extra care must be taken to double and triple check ALL details.

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

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.