37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1048401 |
Time | |
Date | 201211 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZLC.ARTCC |
State Reference | UT |
Environment | |
Flight Conditions | IMC |
Light | Dusk |
Aircraft 1 | |
Make Model Name | Small Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | Direct |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 40 Flight Crew Total 4800 Flight Crew Type 500 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
I set up an approach in the recently installed ifms system. The approach was input for the ILS 20 at cdc using meggi as the IAF. For some reason the ifms system was anticipating a steep turn for the outbound leg of the approach. The center controller commented that it was showing south [me] of course; which I acknowledged. He continued to press me on the variance to direct. I acknowledged that I was seeing the same thing and finally just asked him to cancel that approach and take me to mlf (milford) for the milford transition to the ILS. That is when the problems got bad; I could not get the previous inserted approach out of the ifms system to input a new one. It was not allowing me to remove the old (I am sure it is my lack of experience with the 'button-ology'). The controller was frustrated as was I; so I finally asked for vectors to mlf. He continued to tell me how far off course I was; and asking if I was navigating to mlf. I told him I was trying. I continued to ask for vectors and the controller continued to tell me how far my variance was to the correct course. Our communication was not working well. In the end I arrived at mlf and made the turn back to the 154 to velde; again requesting vectors. The controller continued to give me my variance; but never once (to my memory) gave me a vector to my needed waypoint. I finally arrived at velde and began the approach; when the controller told me to break off the approach and climb to 14;000 ft. I declined. I had used up much of my reserve in the process of finding my way to mlf and back to velde. I told him I was low on fuel and was going to make the approach. He then cleared me for the approach and I successfully flew the approach under less than ideal conditions. I experienced ice; turbulence; and 35 KTS gusting winds.my error was not knowing the ifms system as well as I should have. I did not know how to get rid of the incorrect information on the screen and in the system to re-input the correct information. My only complaint was the controller's lack of willingness to give vectors as requested. I have only had one other situation when I needed the 'urgent help' of a controller. A center controller calmly talked me through a bad case of vertigo. He saved my life. This controller was less than empathetic or helpful.
Original NASA ASRS Text
Title: Pilot of a small jet experienced course deviations on the ILS2 Approach to CDC due to unfamiliarity with a newly installed IFMS system and apparent lack of assistance from ATC.
Narrative: I set up an approach in the recently installed IFMS system. The approach was input for the ILS 20 at CDC using MEGGI as the IAF. For some reason the IFMS system was anticipating a steep turn for the outbound leg of the approach. The Center Controller commented that it was showing south [me] of course; which I acknowledged. He continued to press me on the variance to direct. I acknowledged that I was seeing the same thing and finally just asked him to cancel that approach and take me to MLF (Milford) for the Milford Transition to the ILS. That is when the problems got bad; I could not get the previous inserted approach out of the IFMS system to input a new one. It was not allowing me to remove the old (I am sure it is my lack of experience with the 'button-ology'). The Controller was frustrated as was I; so I finally asked for Vectors to MLF. He continued to tell me how far off course I was; and asking if I was navigating to MLF. I told him I was trying. I continued to ask for vectors and the Controller continued to tell me how far my variance was to the correct course. Our communication was not working well. In the end I arrived at MLF and made the turn back to the 154 to VELDE; again requesting vectors. The Controller continued to give me my variance; but never once (to my memory) gave me a vector to my needed waypoint. I finally arrived at VELDE and began the approach; when the Controller told me to break off the approach and climb to 14;000 FT. I declined. I had used up much of my reserve in the process of finding my way to MLF and back to VELDE. I told him I was low on fuel and was going to make the approach. He then cleared me for the approach and I successfully flew the approach under less than ideal conditions. I experienced ice; turbulence; and 35 KTS gusting winds.My error was not knowing the IFMS system as well as I should have. I did not know how to get rid of the incorrect information on the screen and in the system to re-input the correct information. My only complaint was the Controller's lack of willingness to give vectors as requested. I have only had one other situation when I needed the 'urgent help' of a controller. A Center Controller calmly talked me through a bad case of vertigo. He saved my life. This Controller was less than empathetic or helpful.
Data retrieved from NASA's ASRS site as of July 2013 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.