 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZTL controller voiced concern regarding the lack of compliance with facility directives involving altitudes; coordination and altitude assignments.
| Attributes | |
| ACN | 1040442 |
| Time | |
| Date | 201210 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZTL.ARTCC |
| State Reference | GA |
| Aircraft 1 | |
| Make Model Name | B737-400 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Developmental |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I observed a B737 flight plan in my uret at FL350; sector 27; hampton u-hi; had track control. I observed the B737 in a hand off status to my sector at an interim FL330. Sector 27 still had track control. Sector 22 had approved a point out and released the aircraft to sector 27. Sector 27 never called to gain approval for the aircraft to enter my airspace at FL330; a different stratum. The aircraft didn't come over in a timely manner so I inquired about the apreq when I called to get communications. The controller called me back and advised he 'didn't have to apreq it because the aircraft was level at FL330.' our qa has already determined that any stratum change requires coordination as does our facility operations manual. Earlier in the day; the same sector 'ok'd' FL340 into the data block on an aircraft in the same situation after sector 34 had the hand off at FL350 and descended the aircraft to FL340 without coordination and with head on traffic. I don't know if that situation was reported. This mentality is rampant amongst the area in question and happens constantly. The procedures are there for a reason. Perhaps a pre-duty qa reminder in cedar that stratum change requires coordination is in order.
Original NASA ASRS Text
Title: ZTL Controller voiced concern regarding the lack of compliance with facility directives involving altitudes; coordination and altitude assignments.
Narrative: I observed a B737 flight plan in my URET at FL350; Sector 27; Hampton U-Hi; had track control. I observed the B737 in a hand off status to my sector at an interim FL330. Sector 27 still had track control. Sector 22 had approved a point out and released the aircraft to Sector 27. Sector 27 never called to gain approval for the aircraft to enter my airspace at FL330; a different stratum. The aircraft didn't come over in a timely manner so I inquired about the APREQ when I called to get communications. The Controller called me back and advised he 'didn't have to APREQ it because the aircraft was level at FL330.' Our QA has already determined that any stratum change requires coordination as does our facility operations manual. Earlier in the day; the same sector 'ok'd' FL340 into the Data Block on an aircraft in the same situation after Sector 34 had the hand off at FL350 and descended the aircraft to FL340 without coordination and with head on traffic. I don't know if that situation was reported. This mentality is rampant amongst the area in question and happens constantly. The procedures are there for a reason. Perhaps a pre-duty QA reminder in CEDAR that stratum change requires coordination is in order.
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.