 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Enroute controller described an airspace incursion event when an adjacent controller failed to follow proper procedure claiming he/she observed no traffic and entered the airspace; the reporter questioning the younger controller's safety culture.
| Attributes | |
| ACN | 1074228 |
| Time | |
| Date | 201303 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.ARTCC |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Fighting Falcon F16 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
[Two F16s] were off [to ZZZ] and scheduled to enter the MOA that is in sector xx airspace. The flight was en route and we were steady with traffic working the middle to eastern side of the sector. [The F16s] were coming from northwest and the sector yy controller did not display or coordinate the transition through our airspace. The xx seasoned r-controller pulled up the limited data block in our airspace and said; 'you know sector xx; me; is open here!' the yy controller known for using airspace by 'look and go' said; 'I looked over there and saw you didn't have anything.' the safety culture of younger controllers is such that they think look and go as a limited data block is okay. This is an area that more direct management and awareness needs to be made that it is never acceptable to use anyone's airspace with coordination. The surprise alone is not worth the skipped heart beat that we encounter when a limited is discovered in our airspace.
Original NASA ASRS Text
Title: Enroute Controller described an airspace incursion event when an adjacent Controller failed to follow proper procedure claiming he/she observed no traffic and entered the airspace; the reporter questioning the younger Controller's safety culture.
Narrative: [Two F16s] were off [to ZZZ] and scheduled to enter the MOA that is in Sector XX airspace. The flight was en route and we were steady with traffic working the middle to eastern side of the sector. [The F16s] were coming from northwest and the Sector YY Controller did not display or coordinate the transition through our airspace. The XX seasoned R-Controller pulled up the limited data block in our airspace and said; 'You know Sector XX; me; is open here!' The YY Controller known for using airspace by 'look and go' said; 'I looked over there and saw you didn't have anything.' The safety culture of younger controllers is such that they think look and go as a limited data block is okay. This is an area that more direct management and awareness needs to be made that it is NEVER acceptable to use anyone's airspace with coordination. The surprise alone is not worth the skipped heart beat that we encounter when a limited is discovered in our airspace.
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.