 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Light transport crew canceled IFR and flew VFR in IMC conditions. They cut out a baron to land downwind at trm.
| Attributes | |
| ACN | 466650 |
| Time | |
| Date | 200003 |
| Day | Sun |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : trm.airport |
| State Reference | CA |
| Altitude | agl single value : 500 |
| Environment | |
| Flight Conditions | IMC |
| Weather Elements | Rain |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Light Transport, Low Wing, 2 Turbojet Eng |
| Operating Under FAR Part | Part 91 |
| Navigation In Use | other vortac |
| Flight Phase | descent : approach |
| Route In Use | approach : instrument non precision |
| Flight Plan | VFR |
| Aircraft 2 | |
| Operator | general aviation : personal |
| Make Model Name | Baron 55/Cochise |
| Operating Under FAR Part | Part 91 |
| Flight Phase | descent : approach landing : go around |
| Route In Use | approach : visual |
| Flight Plan | VFR |
| Person 1 | |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : multi engine |
| Experience | flight time total : 6000 |
| ASRS Report | 466650 |
| Person 2 | |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : commercial pilot : instrument |
| Events | |
| Anomaly | inflight encounter : vfr in imc non adherence : published procedure non adherence : far other anomaly other other spatial deviation |
| Independent Detector | other flight crewa other flight crewb |
| Resolutory Action | flight crew : executed go around |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
On IFR flight plan from phx to udd. WX went below IFR minimums at psp and unable to go VFR into udd. Elected to shoot VOR approach into trm and proceed VFR to udd if able, or land at trm. MDA for VOR approach is approximately 380 ft MSL. Broke out of clouds at about 700 ft, elected to land trm due to low ceiling and poor visibility, 2 mi at best in steady rain. After getting trm in sight, first officer canceled IFR with psp approach control, then made announcement of landing on runway 35 at trm. The problem was we were on the wrong frequency. Used udd frequency of 122.8 instead of trm frequency. I saw no targets on our TCASII and landed on runway 35. On landing rollout, a twin baron inbound to land on runway 17 went around, wind favored runway 17, but in light of runway length ceiling and visibility conditions, I elected to land straight in on runway 35. There were no other IFR traffic at the time, because only 1 aircraft can shoot on approach at a time, my aircraft was in error being on the wrong CTAF frequency to make announcements but feel the twin baron should not have been flying around VFR with IFR conditions. I also suspect the twin baron had their transponder off, not allowing me to get a TCASII alert.
Original NASA ASRS Text
Title: LTT CREW CANCELED IFR AND FLEW VFR IN IMC CONDITIONS. THEY CUT OUT A BARON TO LAND DOWNWIND AT TRM.
Narrative: ON IFR FLT PLAN FROM PHX TO UDD. WX WENT BELOW IFR MINIMUMS AT PSP AND UNABLE TO GO VFR INTO UDD. ELECTED TO SHOOT VOR APCH INTO TRM AND PROCEED VFR TO UDD IF ABLE, OR LAND AT TRM. MDA FOR VOR APCH IS APPROX 380 FT MSL. BROKE OUT OF CLOUDS AT ABOUT 700 FT, ELECTED TO LAND TRM DUE TO LOW CEILING AND POOR VISIBILITY, 2 MI AT BEST IN STEADY RAIN. AFTER GETTING TRM IN SIGHT, FO CANCELED IFR WITH PSP APCH CTL, THEN MADE ANNOUNCEMENT OF LNDG ON RWY 35 AT TRM. THE PROB WAS WE WERE ON THE WRONG FREQ. USED UDD FREQ OF 122.8 INSTEAD OF TRM FREQ. I SAW NO TARGETS ON OUR TCASII AND LANDED ON RWY 35. ON LNDG ROLLOUT, A TWIN BARON INBOUND TO LAND ON RWY 17 WENT AROUND, WIND FAVORED RWY 17, BUT IN LIGHT OF RWY LENGTH CEILING AND VISIBILITY CONDITIONS, I ELECTED TO LAND STRAIGHT IN ON RWY 35. THERE WERE NO OTHER IFR TFC AT THE TIME, BECAUSE ONLY 1 ACFT CAN SHOOT ON APCH AT A TIME, MY ACFT WAS IN ERROR BEING ON THE WRONG CTAF FREQ TO MAKE ANNOUNCEMENTS BUT FEEL THE TWIN BARON SHOULD NOT HAVE BEEN FLYING AROUND VFR WITH IFR CONDITIONS. I ALSO SUSPECT THE TWIN BARON HAD THEIR XPONDER OFF, NOT ALLOWING ME TO GET A TCASII ALERT.
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.