37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1694983 |
Time | |
Date | 201910 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | RDM.Airport |
State Reference | OR |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Transport High Wing 2 Turboprop Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Person 2 | |
Function | Captain |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach |
Narrative:
It started when we flew into the redmond area and we were handed over to a new controller. The controller left us high and asked for a 'runway in sight' call 25 nm out. When we couldn't see the airport due to haze; we received a vector towards the dsd VOR and descent to 6;000 feet. At this time; a GA airplane was in the holding pattern over dsd at 6;500 feet. I was about to question ATC; when controller changed the descend-to altitude to 7;000 feet.once the field was in sight; controller cleared us for the visual; leaving us high and too close in to make the approach. We were approved to maneuver for the descent for the visual.while on the visual approach into rdm; a small single engine GA airplane crossed kicby at 5;500 feet; while we were approaching kicby at about 6;200 feet and descending. This resulted in an RA. We complied with the RA; then followed the missed approach procedure after the RA was cleared.ATC failed to be proactive about this traffic; and had left us high and close-in on the visual; vectoring us towards traffic. The traffic alert at kicby was caused by an aircraft that was in contact with ATC and had reported us in sight. This aircraft continued to fly into the final approach course (towards us) and ATC did not take any action to move us or them around.after the missed approach; we received a vector to the west. At this time; the [aircraft] behind us had to go-around as well (ATC cancelled their approach clearance for no apparent reason). Being busy with [aircraft]; it seemed that ATC had forgotten about us; as we were flying towards the mountains at a low altitude. I prompted ATC to turn us inbound again.after landing; taxiing in; we noticed a [turboprop] behind [aircraft] on final aborting the approach. After they landed; the crew expressed that they had received an RA as well. Between the 3 crews; we were very unsatisfied with ATC's performance and regard to safety.a few days ago; ATC was performing below standard in this area as well. Perhaps a lot of new controllers are being trained here? It has been challenging to operate in the redmond area with these controllers.please talk to seattle approach.
Original NASA ASRS Text
Title: Air carrier pilots of separate aircraft reported a loss of separation on approach to RDM airport that resulted in a TCAS RA followed by a go-around.
Narrative: It started when we flew into the Redmond area and we were handed over to a new Controller. The Controller left us high and asked for a 'runway in sight' call 25 nm out. When we couldn't see the airport due to haze; we received a vector towards the DSD VOR and descent to 6;000 feet. At this time; a GA airplane was in the holding pattern over DSD at 6;500 feet. I was about to question ATC; when Controller changed the descend-to altitude to 7;000 feet.Once the field was in sight; Controller cleared us for the visual; leaving us high and too close in to make the approach. We were approved to maneuver for the descent for the visual.While on the visual approach into RDM; a small single engine GA airplane crossed KICBY at 5;500 feet; while we were approaching KICBY at about 6;200 feet and descending. This resulted in an RA. We complied with the RA; then followed the missed approach procedure after the RA was cleared.ATC failed to be proactive about this traffic; and had left us high and close-in on the visual; vectoring us towards traffic. The traffic alert at KICBY was caused by an aircraft that was in contact with ATC and had reported us in sight. This aircraft continued to fly into the final approach course (towards us) and ATC did not take any action to move us or them around.After the missed approach; we received a vector to the west. At this time; the [aircraft] behind us had to go-around as well (ATC cancelled their approach clearance for no apparent reason). Being busy with [aircraft]; it seemed that ATC had forgotten about us; as we were flying towards the mountains at a low altitude. I prompted ATC to turn us inbound again.After landing; taxiing in; we noticed a [turboprop] behind [aircraft] on final aborting the approach. After they landed; the crew expressed that they had received an RA as well. Between the 3 crews; we were very unsatisfied with ATC's performance and regard to safety.A few days ago; ATC was performing below standard in this area as well. Perhaps a lot of new controllers are being trained here? It has been challenging to operate in the Redmond area with these controllers.Please talk to Seattle Approach.
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.