 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZTL controller voiced concern regarding an adjacent controller allegedly 'dressing-up' a data block to indicate procedures were being issued/followed when in fact had not; compromising airspace integrity.
| Attributes | |
| ACN | 1019646 |
| Time | |
| Date | 201206 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZTL.ARTCC |
| State Reference | GA |
| Aircraft 1 | |
| Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I was working the r-side at spartanburg high. I accepted the hand off on a CRJ2 from sector 50 with the aircraft showing at FL270 descending to FL250 in the data block. The SOP between sector 50 and sector 32 requires these aircraft to be level at FL250 when they cross the boundary. The aircraft checked on my frequency at FL270 with no clearance for lower. I had to call and get control and expedite the aircraft through FL260 because I had crossing traffic at FL270. The aircraft missed by six miles. 'Dressing up' data blocks is rampant at ZTL. I don't know for sure that the sector 50 controller did this. Perhaps the pilot of the aircraft missed a clearance. I'm pretty sure the data block was dressed up. If so; this is intentional violation of the 7110.65. Why is it any different than intentionally violating separation standards? It can lead quite quickly to a loss of separation.
Original NASA ASRS Text
Title: ZTL Controller voiced concern regarding an adjacent controller allegedly 'dressing-up' a Data Block to indicate procedures were being issued/followed when in fact had not; compromising airspace integrity.
Narrative: I was working the R-Side at Spartanburg High. I accepted the hand off on a CRJ2 from Sector 50 with the aircraft showing at FL270 descending to FL250 in the Data Block. The SOP between Sector 50 and Sector 32 requires these aircraft to be level at FL250 when they cross the boundary. The aircraft checked on my frequency at FL270 with no clearance for lower. I had to call and get control and expedite the aircraft through FL260 because I had crossing traffic at FL270. The aircraft missed by six miles. 'Dressing up' Data Blocks is rampant at ZTL. I don't know for sure that the Sector 50 Controller did this. Perhaps the pilot of the aircraft missed a clearance. I'm pretty sure the Data Block was dressed up. If so; this is intentional violation of the 7110.65. Why is it any different than intentionally violating separation standards? It can lead quite quickly to a loss of separation.
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.