 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Sct controller described a route discrepancy and incorrect data block information associated with one company that is causing this anomaly.
| Attributes | |
| ACN | 1000041 |
| Time | |
| Date | 201203 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | SCT.TRACON |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Route In Use | STAR FERNANDO5 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach Departure |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| Function | Departure Approach |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
A B737 was at 110. His data block had a trailing right; which is supposed to indicate the aircraft is on an RNAV SID; in this case the CEEME1 arrival. This aircraft was supposed to be on the FERNANDO5 arrival; due to an equipment issue with their fleet. When I inquired as to which arrival the B737 was on; the pilot replied the FERNANDO5 and that they were issued 'a screwed up routing to get there'. I reported the anomaly to my flm; who contacted ZLA. The response was 'the B737 cannot get rid of the trailing right and ZLA will not remove it either. The sct controllers will need to verify that the B737 aircraft have the appropriate arrival. A bad situation gets worse with the CEEME1 arrival. We now have aircraft tagged with one arrival; but on another arrival; but we also need to verify which arrival they actually are on. Turn off the CEEME1 arrival completely until it cannot be fixed. It is a safety hazard in its current form. Tag aircraft that are on a non-RNAV SID appropriately.
Original NASA ASRS Text
Title: SCT Controller described a route discrepancy and incorrect Data Block information associated with one company that is causing this anomaly.
Narrative: A B737 was at 110. His Data Block had a trailing R; which is supposed to indicate the aircraft is on an RNAV SID; in this case the CEEME1 Arrival. This aircraft was supposed to be on the FERNANDO5 Arrival; due to an equipment issue with their fleet. When I inquired as to which arrival the B737 was on; the pilot replied the FERNANDO5 and that they were issued 'a screwed up routing to get there'. I reported the anomaly to my FLM; who contacted ZLA. The response was 'The B737 cannot get rid of the trailing R and ZLA will not remove it either. The SCT Controllers will need to verify that the B737 aircraft have the appropriate arrival. A bad situation gets worse with the CEEME1 Arrival. We now have aircraft tagged with one arrival; but on another arrival; but we also need to verify which arrival they actually are on. Turn off the CEEME1 arrival completely until it cannot be fixed. It is a safety hazard in its current form. Tag aircraft that are on a non-RNAV SID appropriately.
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.