37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1220250 |
Time | |
Date | 201411 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZFW.ARTCC |
State Reference | TX |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
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; dfw departure eld transition checked on I issued a clearance to climb to FL330 but put a temporary altitude of FL310 in the data block. That was my intention to climb the aircraft to flight level 310 because another aircraft was an overflight from the northwest southeast bound I projected the aircraft would be in conflict west of eic (shreveport; la). The whole time I thought I issued flight level 310 to the pilot. As I went to transfer communication to aircraft X I advised him to expect higher on the next frequency but my transmission was blocked by another aircraft. I observed aircraft X mode C change from 310 to 312 I called the next sector eld-H to inquire if they climbed aircraft X; the aircraft had not checked on frequency yet. The controller broadcast to see the pilot was there they acknowledge the controller advised the pilot to maintain FL320 the mode C indicated 322.I have no recommendation I simply made a mistake I knew for sure I issued FL310 but was totally wrong.
Original NASA ASRS Text
Title: ZFW Controller thinks he issued a lower altitude to an aircraft and put that altitude in the data block. Controller ships aircraft to next sector and observes aircraft climbing above altitude that he thought he was assigned.
Narrative: Aircraft X; DFW departure ELD transition checked on I issued a clearance to climb to FL330 but put a temporary altitude of FL310 in the data block. That was my intention to climb the aircraft to flight level 310 because another aircraft was an overflight from the northwest southeast bound I projected the aircraft would be in conflict west of EIC (Shreveport; LA). The whole time I thought I issued flight level 310 to the pilot. As I went to transfer communication to Aircraft X I advised him to expect higher on the next frequency but my transmission was blocked by another aircraft. I observed Aircraft X mode C change from 310 to 312 I called the next sector ELD-H to inquire if they climbed Aircraft X; the aircraft had not checked on frequency yet. The controller broadcast to see the pilot was there they acknowledge the controller advised the pilot to maintain FL320 the mode C indicated 322.I have no recommendation I simply made a mistake I knew for sure I issued FL310 but was totally wrong.
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.