37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 309073 |
Time | |
Date | 199506 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : gjt |
State Reference | CO |
Altitude | msl bound lower : 5800 msl bound upper : 5800 |
Environment | |
Flight Conditions | Marginal |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : gjt |
Operator | common carrier : air taxi |
Make Model Name | Cessna Stationair/Turbo Stationair 6 |
Operating Under FAR Part | Part 135 |
Flight Phase | other |
Flight Plan | None |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Brasilia EMB-120 All Series |
Operating Under FAR Part | Part 135 |
Flight Phase | other |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : single pilot |
Qualification | pilot : cfi pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 200 flight time total : 2200 flight time type : 500 |
ASRS Report | 309073 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | conflict : nmac inflight encounter : vfr in imc inflight encounter : weather |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : exited adverse environment flight crew : took evasive action |
Consequence | Other |
Miss Distance | horizontal : 100 vertical : 100 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I approached from the southwest, contacted the tower with ATIS, and was told to report on left downwind for runway 29. A thunderstorm was to the south of the field near the approach end of runway 29 as well as other scattered storms and rainshowers. I was #2 on downwind with a company 206 in front (no visual contact) and company 206 behind (he had visual contact on me). A commuter brasilia reported a 3 mi final for runway 29. No visual contact was made between any of the traffic and tower lost visual contact with most traffic as rain was moderate to heavy south of the runway. Extending downwind, forward visibility degraded to 1/4 - 1/2 mi. I believe the brasilia was cleared to land and the 206 ahead of me on downwind was told to follow the brasilia. Trying to keep visual contact with the end of runway 29 and with forward visibility too low to see other traffic, I estimated the time it would take the brasilia to make the runway (the company traffic ahead did the same after talking to him afterward), I turned left base. The company traffic following me then transmitted on tower frequency 'nxxx dive -- you've got a brasilia over you.' at this point I did a quick descending left turn as evasive action. I turned and headed directly over runway 04- 22 to avoid runway 29, approach path. The company traffic in front of me ended up in front of the brasilia on final. The brasilia broke off the approach climbing to the right and was told to go around by tower. I asked for and received a left downwind for runway 04 and was then cleared to land runway 04 and landed. The wind was light and variable. I find it hard to believe that, given the WX conditions, the brasilia had visual contact with the runway when asking for and receiving a visual approach to runway 29. I also believe he was much farther out than 3 mi, when he reported so. I also feel the tower should not have used runway 29 for lndgs with the storm at the approach end. The other end of the field was reported as good visibility by another pilot. When all of this occurred, the tower controller finally had other VFR incoming traffic hold VFR outside the air traffic area. I feel this could have been avoided by, 1) asking for an approach to another runway, 2) if this airport had radar services.
Original NASA ASRS Text
Title: NMAC.
Narrative: I APCHED FROM THE SW, CONTACTED THE TWR WITH ATIS, AND WAS TOLD TO RPT ON L DOWNWIND FOR RWY 29. A TSTM WAS TO THE S OF THE FIELD NEAR THE APCH END OF RWY 29 AS WELL AS OTHER SCATTERED STORMS AND RAINSHOWERS. I WAS #2 ON DOWNWIND WITH A COMPANY 206 IN FRONT (NO VISUAL CONTACT) AND COMPANY 206 BEHIND (HE HAD VISUAL CONTACT ON ME). A COMMUTER BRASILIA RPTED A 3 MI FINAL FOR RWY 29. NO VISUAL CONTACT WAS MADE BTWN ANY OF THE TFC AND TWR LOST VISUAL CONTACT WITH MOST TFC AS RAIN WAS MODERATE TO HVY S OF THE RWY. EXTENDING DOWNWIND, FORWARD VISIBILITY DEGRADED TO 1/4 - 1/2 MI. I BELIEVE THE BRASILIA WAS CLRED TO LAND AND THE 206 AHEAD OF ME ON DOWNWIND WAS TOLD TO FOLLOW THE BRASILIA. TRYING TO KEEP VISUAL CONTACT WITH THE END OF RWY 29 AND WITH FORWARD VISIBILITY TOO LOW TO SEE OTHER TFC, I ESTIMATED THE TIME IT WOULD TAKE THE BRASILIA TO MAKE THE RWY (THE COMPANY TFC AHEAD DID THE SAME AFTER TALKING TO HIM AFTERWARD), I TURNED L BASE. THE COMPANY TFC FOLLOWING ME THEN XMITTED ON TWR FREQ 'NXXX DIVE -- YOU'VE GOT A BRASILIA OVER YOU.' AT THIS POINT I DID A QUICK DSNDING L TURN AS EVASIVE ACTION. I TURNED AND HEADED DIRECTLY OVER RWY 04- 22 TO AVOID RWY 29, APCH PATH. THE COMPANY TFC IN FRONT OF ME ENDED UP IN FRONT OF THE BRASILIA ON FINAL. THE BRASILIA BROKE OFF THE APCH CLBING TO THE R AND WAS TOLD TO GAR BY TWR. I ASKED FOR AND RECEIVED A L DOWNWIND FOR RWY 04 AND WAS THEN CLRED TO LAND RWY 04 AND LANDED. THE WIND WAS LIGHT AND VARIABLE. I FIND IT HARD TO BELIEVE THAT, GIVEN THE WX CONDITIONS, THE BRASILIA HAD VISUAL CONTACT WITH THE RWY WHEN ASKING FOR AND RECEIVING A VISUAL APCH TO RWY 29. I ALSO BELIEVE HE WAS MUCH FARTHER OUT THAN 3 MI, WHEN HE RPTED SO. I ALSO FEEL THE TWR SHOULD NOT HAVE USED RWY 29 FOR LNDGS WITH THE STORM AT THE APCH END. THE OTHER END OF THE FIELD WAS RPTED AS GOOD VISIBILITY BY ANOTHER PLT. WHEN ALL OF THIS OCCURRED, THE TWR CTLR FINALLY HAD OTHER VFR INCOMING TFC HOLD VFR OUTSIDE THE ATA. I FEEL THIS COULD HAVE BEEN AVOIDED BY, 1) ASKING FOR AN APCH TO ANOTHER RWY, 2) IF THIS ARPT HAD RADAR SVCS.
Data retrieved from NASA's ASRS site as of July 2007 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.