 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAU controller described a conflict vent when thinking one altitude but issuing a conflicting altitude assignment.
| Attributes | |
| ACN | 1043154 |
| Time | |
| Date | 201210 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZAU.ARTCC |
| State Reference | IL |
| Aircraft 1 | |
| Make Model Name | Citation Excel (C560XL) |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | MD-90 Series (DC-9-90) Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Altitude Overshoot Deviation - Procedural Clearance |
Narrative:
My manual controller pointed out a citation xl to the bae sector descending to FL330 as per the SOP for dtw traffic. The bae controller accepted the point-out reference MD90. My manual controller advised me of the traffic which I observed. I knew I wanted to start citation xl down to FL350 so that we could later give him the standard crossing restriction of FL330. This was a simple case of seeing the traffic at FL330 and issuing the assigned altitude FL330; not FL350 like I wanted to. When I saw citation xl descending through what I thought the assigned altitude of FL350 I had the aircraft maintain his present altitude (FL347). It was too late the aircraft was already through FL340 so I climbed him back up to FL340. When I later listened to the pilot read back; I realized what I had done. Occasionally a controller will do what I did; observe the aircraft's altitude that they are supposed to miss and still issue the very same altitude.
Original NASA ASRS Text
Title: ZAU Controller described a conflict vent when thinking one altitude but issuing a conflicting altitude assignment.
Narrative: My Manual Controller pointed out a Citation XL to the BAE Sector descending to FL330 as per the SOP for DTW traffic. The BAE Controller accepted the point-out reference MD90. My Manual Controller advised me of the traffic which I observed. I knew I wanted to start Citation XL down to FL350 so that we could later give him the standard crossing restriction of FL330. This was a simple case of seeing the traffic at FL330 and issuing the assigned altitude FL330; not FL350 like I wanted to. When I saw Citation XL descending through what I thought the assigned altitude of FL350 I had the aircraft maintain his present altitude (FL347). It was too late the aircraft was already through FL340 so I climbed him back up to FL340. When I later listened to the pilot read back; I realized what I had done. Occasionally a controller will do what I did; observe the aircraft's altitude that they are supposed to miss and still issue the very same altitude.
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.