 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Bos controller voiced concern regarding the frequent incorrect read backs of assigned sids; noting fixes on the SID and the SID names are very confusing and errors difficult to detect during on clearance delivery read backs.
| Attributes | |
| ACN | 940546 |
| Time | |
| Date | 201103 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | BOS.Tower |
| State Reference | MA |
| Aircraft 1 | |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Route In Use | SID LOGAN SIX |
| Flight Plan | IFR |
| Person 1 | |
| Function | Flight Data / Clearance Delivery |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Multiple aircraft are reading back the wrong departures off all runways at logan. We have multiple sids off all different runways and the fixes along the routes are named after the sids. When departing off runway 33L tonight we were using a non RNAV SID. We issued the logan six departure then the first fix. The first fix on the route is the name of another SID off another runway. The pilots are not saying they are on the logan six. They are saying they are on the patts departure and the clearance delivery controller has to catch this on the read back. This has created tons of work for the clearance delivery position; its time to stop all these departures until we can implement all the sids for rnavs at one time. Managers at boston have said this will never happen because we are mandated by the city courts to do this for noise abatement. It's a matter of time before two aircraft collide because of this nonsense. I was getting a read back from an A319 and the pilot said they were on the hylnd departure when in fact they were on the logan six departure. Recommendation; stop all these different departures until we can implement all the sids at one time.
Original NASA ASRS Text
Title: BOS Controller voiced concern regarding the frequent incorrect read backs of assigned SIDS; noting fixes on the SID and the SID names are very confusing and errors difficult to detect during on Clearance Delivery read backs.
Narrative: Multiple aircraft are reading back the wrong departures off all runways at Logan. We have multiple SIDS off all different runways and the fixes along the routes are named after the SIDS. When departing off Runway 33L tonight we were using a non RNAV SID. We issued the Logan Six Departure then the first fix. The first fix on the route is the name of another SID off another runway. The pilots are not saying they are on the Logan Six. They are saying they are on the PATTS Departure and the Clearance Delivery Controller has to catch this on the read back. This has created tons of work for the Clearance Delivery position; its time to stop all these departures until we can implement all the SIDS for RNAVS at one time. Managers at Boston have said this will never happen because we are mandated by the City Courts to do this for noise abatement. It's a matter of time before two aircraft collide because of this nonsense. I was getting a read back from an A319 and the Pilot said they were on the HYLND Departure when in fact they were on the Logan Six Departure. Recommendation; stop all these different departures until we can implement all the SIDS at one time.
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.