 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZID controller reports of having to coordinate higher for an aircraft and the sector he calls has to coordinate with another sector to get approval.
| Attributes | |
| ACN | 1218552 |
| Time | |
| Date | 201411 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZID.ARTCC |
| State Reference | IN |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 15 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
Aircraft X came over at FL190. I thought this was a pretty low altitude to go all the way to florida so I asked if that was his requested final. He indicated it wasn't and wanted FL370. At the time the conversation with aircraft X ended dnv sector called to let me know that another carrier was on a heading for hilltop MOA. I accepted the coordination and while they were still on the land line requested higher for aircraft X to FL230. The controller said that they would have to call eon sector to get control on aircraft X and would call me back. They did call back and release higher. This is the same situation we have encountered before and will continue to encounter until something is done with the airspace that dnv releases to eon sector. In my opinion it is completely unacceptable that when I'm talking to the sector that is supposed to own the airspace I'm coordinating about can't make a simple decision and has to call another sector for approval. All of this could be solved with a simple flash through procedure between dnv and eon. Eon makes a hand off to dnv if dnv doesn't have traffic they make a hand off to bvt and when bvt takes the hand off eon switches the aircraft to bvt. If traffic is a factor then dnv coordinates with eon sector prior to accepting the hand off. It really is this simple.
Original NASA ASRS Text
Title: ZID Controller reports of having to coordinate higher for an aircraft and the sector he calls has to coordinate with another sector to get approval.
Narrative: Aircraft X came over at FL190. I thought this was a pretty low altitude to go all the way to Florida so I asked if that was his requested final. He indicated it wasn't and wanted FL370. At the time the conversation with Aircraft X ended DNV sector called to let me know that another carrier was on a heading for Hilltop MOA. I accepted the coordination and while they were still on the land line requested higher for Aircraft X to FL230. The controller said that they would have to call EON sector to get control on Aircraft X and would call me back. They did call back and release higher. This is the same situation we have encountered before and will continue to encounter until something is done with the airspace that DNV releases to EON sector. In my opinion it is completely unacceptable that when I'm talking to the sector that is supposed to own the airspace I'm coordinating about can't make a simple decision and has to call another sector for approval. All of this could be solved with a simple flash through procedure between DNV and EON. EON makes a hand off to DNV if DNV doesn't have traffic they make a hand off to BVT and when BVT takes the hand off EON switches the aircraft to BVT. If traffic is a factor then DNV coordinates with EON sector prior to accepting the hand off. It really is this simple.
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.