37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1336965 |
Time | |
Date | 201602 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | MTJ.Airport |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Light Transport High Wing 2 Turboprop Eng |
Flight Phase | Climb |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 210 Flight Crew Type 5178 |
Events | |
Anomaly | Conflict Airborne Conflict Conflict NMAC Deviation - Procedural Published Material / Policy |
Narrative:
We were talking to den center while going into mtj. Descending into bruuk on the arrival we were cleared for the visual approach to runway 17. Center told us about traffic in the area which we had on TCAS west of bruuk headed east with no altitude read out. The traffic was moving very slowly. We could not tell their intentions at that point. My first officer (first officer) was making position reports and saying that we were landing on 17 but the other aircraft never made a position report nor did he state his intentions. As we approached bruuk while descending to 9;000 feet I started to turn to the right (northwest) as the other aircraft kept coming toward bruuk also. Just then we got a TA for 'traffic; traffic'. I continued northwest till well clear but did not feel comfortable making a 360 because of the terrain. I then turned south and paralleled the course and was going to follow the missed approach procedure. Although; the other aircraft was so slow that we passed him very quickly and re-intercepted the final and safely landed the plane on 17. The other aircraft; which was a [light twin]; finally made a position report when we were well ahead of him. My first officer had been making position reports the entire time.it happened again [on another flight]; [and] the same [light twin] had a very close encounter with this flight also. Three days in a row; the same aircraft all had close encounters on the arrival with the same [light twin]. All 3 flights had to do maneuvers to avoid the traffic. I was sitting in a window seat on my DH back out to mtj. I felt the avoidance maneuver and saw the [light twin] right outside my window. It was as close as I have ever been to another aircraft while airborne. I feel that we need a part time tower put in place for this airport at least on weekends. It is; in my opinion; the most dangerous airport that I fly into. When we left that day there were aircraft taking off and landing in different direction on runway 17 and 35. That coupled with the lack of position reports is a situation being set up for an accident.
Original NASA ASRS Text
Title: Air carrier Captain reported taking evasive action to avoid a light twin aircraft while on approach at MTJ; and stated the same aircraft has caused problems in the past.
Narrative: We were talking to DEN center while going into MTJ. Descending into BRUUK on the arrival we were cleared for the visual approach to Runway 17. Center told us about traffic in the area which we had on TCAS west of BRUUK headed east with no altitude read out. The traffic was moving very slowly. We could not tell their intentions at that point. My First Officer (FO) was making position reports and saying that we were landing on 17 but the other aircraft never made a position report nor did he state his intentions. As we approached BRUUK while descending to 9;000 feet I started to turn to the right (northwest) as the other aircraft kept coming toward BRUUK also. Just then we got a TA for 'traffic; traffic'. I continued northwest till well clear but did not feel comfortable making a 360 because of the terrain. I then turned south and paralleled the course and was going to follow the missed approach procedure. Although; the other aircraft was so slow that we passed him very quickly and re-intercepted the final and safely landed the plane on 17. The other aircraft; which was a [light twin]; finally made a position report when we were well ahead of him. My FO had been making position reports the entire time.It happened again [on another flight]; [and] the same [light twin] had a very close encounter with this flight also. Three days in a row; the same aircraft all had close encounters on the arrival with the same [light twin]. All 3 flights had to do maneuvers to avoid the traffic. I was sitting in a window seat on my DH back out to MTJ. I felt the avoidance maneuver and saw the [light twin] right outside my window. It was as close as I have ever been to another aircraft while airborne. I feel that we need a part time tower put in place for this airport at least on weekends. It is; in my opinion; the most dangerous airport that I fly into. When we left that day there were aircraft taking off and landing in different direction on Runway 17 and 35. That coupled with the lack of position reports is a situation being set up for an accident.
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.