37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1428737 |
Time | |
Date | 201703 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | P80.TRACON |
State Reference | OR |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Working hood sector end of shift; north sector was about to go over 2 hours right as an arrival rush was incoming. Supervisor had me take in north until next crew came in to split it off again. Got busy with arrivals and departures; aircraft trying to talk same time different frequencies making me have to decipher who was calling. Aircraft X departed; was one of the cross frequencies said climbing to 10000 ft. I hadn't given anyone 10000 ft the entire session so it caught my ear in the mixed transmissions. I asked who it was and it was aircraft X. I radared; they asked; verify we are assigned 10000 ft; I said negative; maintain 6000 ft. Pilot was going through 5800 said going to go through but we can go back down; I told them that's fine; maintain 7000; they read it back. A few moments later I planned to tunnel them and an aircraft under my rho arrivals and get them out of my departure corridor; but after I turned them north to go under the arrival; I noticed they were at 7700; I immediately turned right heading 120 and told descend and maintain 7000 immediately. Pilot asked '7000?' I said affirmative; maintain 7000 immediately. Turned an aircraft off the arrival slightly just in case at 8000 until both were separated and sent back to the downwind to final. They were anywhere between 1.8 and 2 miles lateral and 400-600 ft vertically separated. The supervisor already apologized that he should not have combined sectors; bit the bullet and left north on for over 2 hrs and said he learned his lesson that maybe call tower to give more spacing on the departures instead of launching the fleet with bad timing when we have to combine sectors and busy with an arrival rush on multiple frequencies. The pilot said he was confused because the PDX1 departure does not have an assigned altitude with it like the rnavs do and was climbing to his filed alt; so maybe 6000 ft could be added to that to avoid confusion. But at same time the tower had given them 6000 ft at clearance and this mostly isn't an issue. If I had noticed earlier that he was busting his altitude; I would not have turned him north and would might have kept 3 miles lateral separation though they looked like they might have been heading slightly into the rho arrival route anyways. So I missed that part too expecting him to level off at 7000.
Original NASA ASRS Text
Title: Portland TRACON Controller reported a loss of separation due to an aircraft overshooting assigned altitude.
Narrative: Working Hood sector end of shift; North sector was about to go over 2 hours right as an arrival rush was incoming. Supervisor had me take in North until next crew came in to split it off again. Got busy with arrivals and departures; aircraft trying to talk same time different frequencies making me have to decipher who was calling. Aircraft X departed; was one of the cross frequencies said climbing to 10000 ft. I hadn't given anyone 10000 ft the entire session so it caught my ear in the mixed transmissions. I asked who it was and it was Aircraft X. I RADARed; they asked; verify we are assigned 10000 ft; I said negative; maintain 6000 ft. Pilot was going through 5800 said going to go through but we can go back down; I told them that's fine; maintain 7000; they read it back. A few moments later I planned to tunnel them and an aircraft under my RHO arrivals and get them out of my departure corridor; but after I turned them north to go under the arrival; I noticed they were at 7700; I immediately turned right heading 120 and told descend and maintain 7000 immediately. Pilot asked '7000?' I said affirmative; maintain 7000 immediately. Turned an aircraft off the arrival slightly just in case at 8000 until both were separated and sent back to the downwind to final. They were anywhere between 1.8 and 2 miles lateral and 400-600 ft vertically separated. The supervisor already apologized that he should not have combined sectors; bit the bullet and left North on for over 2 hrs and said he learned his lesson that maybe call tower to give more spacing on the departures instead of launching the fleet with bad timing when we have to combine sectors and busy with an arrival rush on multiple frequencies. The pilot said he was confused because the PDX1 departure does not have an assigned altitude with it like the RNAVs do and was climbing to his filed alt; so maybe 6000 ft could be added to that to avoid confusion. But at same time the Tower had given them 6000 ft at clearance and this mostly isn't an issue. If I had noticed earlier that he was busting his altitude; I would not have turned him north and would might have kept 3 miles lateral separation though they looked like they might have been heading slightly into the RHO arrival route anyways. So I missed that part too expecting him to level off at 7000.
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.