37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 951489 |
Time | |
Date | 201105 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZHN.ARTCC |
State Reference | HI |
Aircraft 1 | |
Make Model Name | B717 (Formerly MD-95) |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B717 (Formerly MD-95) |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
[I was] working R4 at hcf; enroute side; which includes airspace that feeds hnl approach from southeast as well as sequencing into ogg; with additional over flights that cross/climb through that are heading to koa and ito. I was working R4 without a d-side which is the standard. My active bay was filled all the way up with strips; the supervisor even asked if I would like a d-side; and I said no. The first B717 [was] westbound landing hnl from ito 10 east of lny at 280 asking for lower. A second B717 southwest bound to koa out of 210 climbing to 230 wasn't laterally separated. I sent out my 1 minute at 2 minute leader lines to see that the first B717 would be abeam his company at 1.5 minutes. I hesitate then give the first B717 clearance through his altitude. I was betting on standard descent. One minute later the second B717; level 230; said he was responding to an RA; I pointed out the B717 10 o'clock 3 miles 250 descending. Seconds later he reported seeing him passing. The B717 was descending at a faster than normal descent rate. I told the supervisor; they pulled the raptor and showed me that at 1 sweep I had 3 miles and 1;200 ft and the next sweep was 5 miles with only 800 ft vertical. I was lucky to keep separation. I made the mistake of not using positive separation with crossing traffic. I knew the situation was unsafe and choose to monitor the situation but then never reacted when the situation became unsafe. It was a horrible technique. If I felt it was a priority to get the first B717 down I should have placed him on a vector right of course to keep him clear of traffic then when he is beneath him he could have went more direct; or just let him level at 240 and once clear he could have had lower. It was an error in judgment and will not be repeated. It was a sloppy session and I have to address that every time I plug in; my head has to be in there 100 percent regardless of what is going on personal matters. I also believe that I don't have to be macho and can ask for a d-side if I do feel like it will be getting busy.
Original NASA ASRS Text
Title: HCF Controller described a TCAS RA event when separation judgement involving crossing Air Carrier traffic was flawed and descent rate was slower than anticipated.
Narrative: [I was] working R4 at HCF; enroute side; which includes airspace that feeds HNL Approach from southeast as well as sequencing into OGG; with additional over flights that cross/climb through that are heading to KOA and ITO. I was working R4 without a D-Side which is the standard. My active bay was filled all the way up with strips; the supervisor even asked if I would like a D-Side; and I said NO. The first B717 [was] westbound landing HNL from ITO 10 east of LNY at 280 asking for lower. A second B717 southwest bound to KOA out of 210 climbing to 230 wasn't laterally separated. I sent out my 1 minute at 2 minute leader lines to see that the first B717 would be abeam his company at 1.5 minutes. I hesitate then give the first B717 clearance through his altitude. I was betting on standard descent. One minute later the second B717; level 230; said he was responding to an RA; I pointed out the B717 10 o'clock 3 miles 250 descending. Seconds later he reported seeing him passing. The B717 was descending at a faster than normal descent rate. I told the supervisor; they pulled the Raptor and showed me that at 1 sweep I had 3 miles and 1;200 FT and the next sweep was 5 miles with only 800 FT vertical. I was lucky to keep separation. I made the mistake of not using positive separation with crossing traffic. I knew the situation was unsafe and choose to monitor the situation but then never reacted when the situation became unsafe. It was a horrible technique. If I felt it was a priority to get the first B717 down I should have placed him on a vector right of course to keep him clear of traffic then when he is beneath him he could have went more direct; or just let him level at 240 and once clear he could have had lower. It was an error in judgment and will not be repeated. It was a sloppy session and I have to address that every time I plug in; my head has to be in there 100 percent regardless of what is going on personal matters. I also believe that I don't have to be macho and can ask for a D-Side if I do feel like it will be getting busy.
Data retrieved from NASA's ASRS site as of April 2012 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.