37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1416806 |
Time | |
Date | 201701 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZDV.ARTCC |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
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 | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Trainee Enroute |
Qualification | Air Traffic Control Developmental |
Person 2 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Type 886 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Undershoot Deviation - Procedural Published Material / Policy |
Narrative:
I was the controller training on the sector. The traffic volume and complexity began to pick up due to turbulent ride conditions and an aircraft that I was in communication with making accidental transmissions over guard which indicated a medical problem on board. Aircraft X came onto the frequency after taking the handoff from sector 07. Upon check-on aircraft X asked about ride conditions at 37000 feet. I responded that 37000 feet was reporting occasional light chop and aircraft X then requested a climb to that altitude. I observed traffic in front of aircraft X opposite direction at 36000 feet and gave aircraft X a clearance to climb to reach 37000 feet in 2 minutes or less. The pilot read back the clearance correctly and at this point had 40 miles of separation with 3 minutes before 5 miles of separation would be lost. At this time I began trying to gather information on what was potentially a medical emergency being broadcast over guard by another aircraft whom I also had on my frequency. Scanning back to aircraft X the climb rate indicated he would easily make his restriction but after a few more transmissions I observed that aircraft X had leveled out at 36600 feet. After observing this; I issued aircraft Y a descent to 35000 feet to achieve separation but the pilot than hesitated saying; 'descending in response to a TCAS.' aircraft Y at this time had still not actually began a descent according to our radar display and my trainer than keyed up to issue a descent clearance once more. The aircraft broke required separation with 4.7 miles and 800 feet. Aircraft X reached 37000 feet 3:20 minutes after reading back the restriction. In this event; I would like that the pilot be instructed that if he cannot meet a climb restriction to advise as soon as possible so an alternative action can be taken immediately.
Original NASA ASRS Text
Title: ZDV Controller and the flight crew involved reported they did not comply with a clearance to be level at an altitude in two minutes or less. A loss of separation with opposite direction traffic resulted.
Narrative: I was the controller training on the sector. The traffic volume and complexity began to pick up due to turbulent ride conditions and an aircraft that I was in communication with making accidental transmissions over guard which indicated a medical problem on board. Aircraft X came onto the frequency after taking the handoff from Sector 07. Upon check-on Aircraft X asked about ride conditions at 37000 feet. I responded that 37000 feet was reporting occasional light chop and Aircraft X then requested a climb to that altitude. I observed traffic in front of Aircraft X opposite direction at 36000 feet and gave Aircraft X a clearance to climb to reach 37000 feet in 2 minutes or less. The pilot read back the clearance correctly and at this point had 40 miles of separation with 3 minutes before 5 miles of separation would be lost. At this time I began trying to gather information on what was potentially a medical emergency being broadcast over guard by another aircraft whom I also had on my frequency. Scanning back to Aircraft X the climb rate indicated he would easily make his restriction but after a few more transmissions I observed that Aircraft X had leveled out at 36600 feet. After observing this; I issued Aircraft Y a descent to 35000 feet to achieve separation but the pilot than hesitated saying; 'Descending in response to a TCAS.' Aircraft Y at this time had still not actually began a descent according to our RADAR display and my trainer than keyed up to issue a descent clearance once more. The aircraft broke required separation with 4.7 miles and 800 feet. Aircraft X reached 37000 feet 3:20 minutes after reading back the restriction. In this event; I would like that the pilot be instructed that if he cannot meet a climb restriction to advise as soon as possible so an alternative action can be taken immediately.
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.