 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZDC center controller and flight crew reported the aircraft turned early on an RNAV SID.
| Attributes | |
| ACN | 1478807 |
| Time | |
| Date | 201709 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | CLT.Airport |
| State Reference | VA |
| Aircraft 1 | |
| Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | SID BARMY3 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute Supervisor / CIC |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7.0 |
| Person 2 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
The raleigh/liberty (R36/27) controller notified me that aircraft X took an early turn to the northeast towards rdu on the BARMY3 SID out of clt. The controller questioned the pilot who corrected course. The pilot said it may be an FMS issue. I requested the pilot called the area 2 desk when they reached their destination.a pilot for aircraft X called and gave further details to a possible FMS issue. The pilots accepted the correct routing (kclt.BARMY3.rdu [route to destination]) with a runway 18L departure. The runway assignment was changed to runway 18C and the pilot may have not had time to verify waypoints; which should have been the same. The pilot thought the runway change may have dropped waypoints (barmy or batta); which caused the early turn to rdu.the issue was highlighted as the event of aircraft turning off of barmy SID to points north has happened with enough frequency to question. Sometimes (not in this case) these early turns put aircraft into the rdu shelf (FL240-260); where rdu departures climb off the shprd SID head-on.the event was forward to ZDC tmu who inquired with company dispatch to see if FMS problems on the barmy SID was a known issue; or if this was something new.this report is being written with hopes of identifying the source of barmy SID turn issue. Is it clearance delivery; FMS; or pilot-action driven?
Original NASA ASRS Text
Title: ZDC Center Controller and flight crew reported the aircraft turned early on an RNAV SID.
Narrative: The Raleigh/Liberty (R36/27) Controller notified me that Aircraft X took an early turn to the northeast towards RDU on the BARMY3 SID out of CLT. The controller questioned the pilot who corrected course. The pilot said it may be an FMS issue. I requested the pilot called the Area 2 desk when they reached their destination.A pilot for Aircraft X called and gave further details to a possible FMS issue. The pilots accepted the correct routing (KCLT.BARMY3.RDU [route to destination]) with a Runway 18L departure. The runway assignment was changed to Runway 18C and the pilot may have not had time to verify waypoints; which should have been the same. The pilot thought the runway change may have dropped waypoints (BARMY or BATTA); which caused the early turn to RDU.The issue was highlighted as the event of aircraft turning off of BARMY SID to points North has happened with enough frequency to question. Sometimes (not in this case) these early turns put aircraft into the RDU shelf (FL240-260); where RDU departures climb off the SHPRD SID head-on.The event was forward to ZDC TMU who inquired with company dispatch to see if FMS problems on the BARMY SID was a known issue; or if this was something new.This report is being written with hopes of identifying the source of BARMY SID turn issue. Is it clearance delivery; FMS; or pilot-action driven?
Data retrieved from NASA's ASRS site 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.