 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
EA50 pilot reported that ATC did a poor job of vectoring them for the approach.
| Attributes | |
| ACN | 1651158 |
| Time | |
| Date | 201905 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | MYF.Airport |
| State Reference | CA |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Eclipse 500 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Final Approach Initial Approach |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Single Pilot |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 25 Flight Crew Total 3900 Flight Crew Type 1100 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach |
Narrative:
I was being vectored for the ILS approach. I was told to keep my speed at 250 knots. I was kept high and given an intercept vector for the localizer that was perpendicular to the inbound course. There was no way this aircraft wouldn't fly through the localizer at that speed and I told the controller that I needed to fly a different vector and he said no and then gave me a vector and a speed that didn't help because I was already intercepting. I saved the localizer part of the approach but the controller didn't clear me for the approach until long after the glide slope dropped out of sight. In fact he forgot to clear me for the approach so I told him that I converted the approach to a localizer approach because he screwed up the glide slope but at the 170 knot speed he gave me for final I was over the airport when I broke out of the clouds. Not wanting to let that controller have another shot at killing me I told the tower to cancel my IFR and I'd fly the traffic pattern which I did and landed. I asked ground control to get me a phone number for the TRACON and left a stinging message for the ATC chief. I told the ATC chief message machine that the controller needed training.
Original NASA ASRS Text
Title: EA50 pilot reported that ATC did a poor job of vectoring them for the approach.
Narrative: I was being vectored for the ILS approach. I was told to keep my speed at 250 Knots. I was kept high and given an intercept vector for the localizer that was perpendicular to the inbound course. There was no way this aircraft wouldn't fly through the localizer at that speed and I told the Controller that I needed to fly a different vector and he said no and then gave me a vector and a speed that didn't help because I was already intercepting. I saved the localizer part of the approach but the Controller didn't clear me for the approach until long after the glide slope dropped out of sight. In fact he forgot to clear me for the approach so I told him that I converted the approach to a localizer approach because he screwed up the glide slope but at the 170 knot speed he gave me for final I was over the airport when I broke out of the clouds. Not wanting to let that controller have another shot at killing me I told the tower to cancel my IFR and I'd fly the traffic pattern which I did and landed. I asked Ground Control to get me a phone number for the TRACON and left a stinging message for the ATC Chief. I told the ATC Chief message machine that the controller needed training.
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.