37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1046555 |
Time | |
Date | 201211 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZDC.ARTCC |
State Reference | VA |
Aircraft 1 | |
Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
Flight Phase | Climb |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Developmental |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
Crj-200 was climbing westbound. He was at FL340 when I inquired what his estimated time to reach FL380 would be. He said a little more than 4 minutes. His traffic was a point out from ZID; an A320 at FL370. I issued crj-200 a climb to FL380 and monitored his progress. When he was at FL360; I issued a rate of climb of 1;000 FPM. He acknowledged my request. At FL375; crj-200 indicates he is not longer able to keep the 1;000 FPM. I acknowledge and ask what can he do on climb and do not get an answer; then I ask again if he is climbing at all; he stated; 'we are getting our speed up;' I then ask him to turn 40 degrees left for traffic and climb to FL380. I then called ZID to inform them what was happening. I had a j-ring on crj-200; and before losing separation; I witnessed FL380 in my data block. I then re-cleared the crj-200 to hnn and shipped him to ZID. Sequence traffic at altitude and leave crj-200 at FL360 and let ZID climb him. I know there was a work group investigating the phraseology linked to timed climbs to make it more useful and understandable for controllers and pilots. Something to the effect of 'climb to reach FL380 in 4 minutes of less' with no time stamp requirement would be nice.
Original NASA ASRS Text
Title: ZDC Controller described a loss of separation event listing the current required phraseology related to climb instructions as as contributing to this event and recommending changes to the current procedure.
Narrative: CRJ-200 was climbing westbound. He was at FL340 when I inquired what his estimated time to reach FL380 would be. He said a little more than 4 minutes. His traffic was a point out from ZID; an A320 at FL370. I issued CRJ-200 a climb to FL380 and monitored his progress. When he was at FL360; I issued a rate of climb of 1;000 FPM. He acknowledged my request. At FL375; CRJ-200 indicates he is not longer able to keep the 1;000 FPM. I acknowledge and ask what can he do on climb and do not get an answer; then I ask again if he is climbing at all; he stated; 'We are getting our speed up;' I then ask him to turn 40 degrees left for traffic and climb to FL380. I then called ZID to inform them what was happening. I had a j-ring on CRJ-200; and before losing separation; I witnessed FL380 in my data block. I then re-cleared the CRJ-200 to HNN and shipped him to ZID. Sequence traffic at altitude and leave CRJ-200 at FL360 and let ZID climb him. I know there was a work group investigating the phraseology linked to timed climbs to make it more useful and understandable for controllers and pilots. Something to the effect of 'climb to reach FL380 in 4 minutes of less' with no time stamp requirement would be nice.
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.