 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
IFR departure from mbl is questioned by ATC regarding heading/clearance; pilot voiced concern regarding communication procedures used to obtain IFR clrncs.
| Attributes | |
| ACN | 798042 |
| Time | |
| Date | 200808 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : mbl.airport |
| State Reference | MI |
| Altitude | msl single value : 8000 |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zmp.artcc artcc : zzz.artcc |
| Operator | general aviation : corporate |
| Make Model Name | Citation Excel |
| Operating Under FAR Part | Part 91 |
| Flight Phase | climbout : intermediate altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : commercial pilot : cfi pilot : atp pilot : multi engine |
| Experience | flight time last 90 days : 60 flight time total : 3100 flight time type : 1000 |
| ASRS Report | 798042 |
| Events | |
| Anomaly | non adherence : clearance other spatial deviation |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Supplementary | |
| Problem Areas | Navigational Facility Flight Crew Human Performance |
| Primary Problem | Navigational Facility |
Narrative:
When taxiing out to depart mbl; we could not get ZMP on the frequency given. We had to revert to using transmit and guard frequencys as published on the chart. This used the VOR 111.4 as the receive frequency and 122.1 as the transmit. The problem with that is that AWOS is also transmitted over the same frequency 114.1. With the AWOS continually playing it makes it difficult to distinguish from a transmission. We received and read back our clearance; we were released for takeoff and departed according to the clearance. When we contacted center; they questioned our clearance. Center asked if we were assigned a heading of 270 degrees. We were basically headed in the opposite direction headed to piker intersection. It is my opinion that with both AWOS and FSS transmitting over the same frequency at the same time is confusing. Receiving and reading back clrncs are critical elements of safe flight; and communications for these elements should be clear and concise without any other distrs. I'm sure this isn't the only airport that has this problem.
Original NASA ASRS Text
Title: IFR DEP FROM MBL IS QUESTIONED BY ATC REGARDING HEADING/CLRNC; PLT VOICED CONCERN REGARDING COM PROCS USED TO OBTAIN IFR CLRNCS.
Narrative: WHEN TAXIING OUT TO DEPART MBL; WE COULD NOT GET ZMP ON THE FREQ GIVEN. WE HAD TO REVERT TO USING XMIT AND GUARD FREQS AS PUBLISHED ON THE CHART. THIS USED THE VOR 111.4 AS THE RECEIVE FREQ AND 122.1 AS THE XMIT. THE PROB WITH THAT IS THAT AWOS IS ALSO XMITTED OVER THE SAME FREQ 114.1. WITH THE AWOS CONTINUALLY PLAYING IT MAKES IT DIFFICULT TO DISTINGUISH FROM A XMISSION. WE RECEIVED AND READ BACK OUR CLRNC; WE WERE RELEASED FOR TKOF AND DEPARTED ACCORDING TO THE CLRNC. WHEN WE CONTACTED CTR; THEY QUESTIONED OUR CLRNC. CTR ASKED IF WE WERE ASSIGNED A HDG OF 270 DEGS. WE WERE BASICALLY HEADED IN THE OPPOSITE DIRECTION HEADED TO PIKER INTXN. IT IS MY OPINION THAT WITH BOTH AWOS AND FSS XMITTING OVER THE SAME FREQ AT THE SAME TIME IS CONFUSING. RECEIVING AND READING BACK CLRNCS ARE CRITICAL ELEMENTS OF SAFE FLT; AND COMS FOR THESE ELEMENTS SHOULD BE CLR AND CONCISE WITHOUT ANY OTHER DISTRS. I'M SURE THIS ISN'T THE ONLY ARPT THAT HAS THIS PROB.
Data retrieved from NASA's ASRS site as of May 2009 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.