 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Ord local controller reported issuing an aircraft a go-around was then issued nonstandard go-around instructions by the departure controller.
| Attributes | |
| ACN | 1443851 |
| Time | |
| Date | 201704 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ORD.Tower |
| State Reference | IL |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Ground Event / Encounter Person / Animal / Bird |
Narrative:
A departure reported hitting a coyote on runway 9L resulting in the runway being closed. The following aircraft; aircraft X; was instructed to execute a missed approach. After coordinating with the runway 9R controller; I issued an interim 040 heading and climb to 4000 feet followed by a turn to 320 (which was the coordinated heading with 9R). After issuing the final turn; I instructed aircraft X to contact departure. Following aircraft X; aircraft Y was also given missed approach instructions and issued heading 040 to get in trail of aircraft X. At this time; I noticed aircraft X had remained on the 040 heading. Aircraft Y was approximately 4 miles behind aircraft X and nearing the boundary of my airspace and the only other aircraft in the vicinity was not in conflict with either missed approach; so I chose to ship aircraft Y to departure before coordinating with other local controllers which was done. After coordinating with the departure controller; I learned aircraft X was instructed to fly 040 and climb to 6000 feet. While this is not standard practice; aircraft X was out of the tower's airspace so not technically wrong.better understanding between ord tower and C90 regarding missed approaches and why things are done certain ways would help.
Original NASA ASRS Text
Title: ORD Local Controller reported issuing an aircraft a go-around was then issued nonstandard go-around instructions by the Departure Controller.
Narrative: A departure reported hitting a coyote on Runway 9L resulting in the runway being closed. The following aircraft; Aircraft X; was instructed to execute a missed approach. After coordinating with the Runway 9R controller; I issued an interim 040 heading and climb to 4000 feet followed by a turn to 320 (which was the coordinated heading with 9R). After issuing the final turn; I instructed Aircraft X to contact departure. Following Aircraft X; Aircraft Y was also given missed approach instructions and issued heading 040 to get in trail of Aircraft X. At this time; I noticed Aircraft X had remained on the 040 heading. Aircraft Y was approximately 4 miles behind Aircraft X and nearing the boundary of my airspace and the only other aircraft in the vicinity was not in conflict with either missed approach; so I chose to ship Aircraft Y to departure before coordinating with other local controllers which was done. After coordinating with the departure controller; I learned Aircraft X was instructed to fly 040 and climb to 6000 feet. While this is not standard practice; Aircraft X was out of the tower's airspace so not technically wrong.Better understanding between ORD Tower and C90 regarding missed approaches and why things are done certain ways would help.
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.