2010-01 · NASA ASRS report 867648
BIL Local Controller described low altitude alert event when aircraft's descent on the VOR/DME Runway 28 approach activated the alarm; pilot acknowledging that the GPS was programed incorrectly prompting the early descent.
I took Local Control and was briefed that Aircraft X was approved for opposite direction practice approach (IMC). The relieved controller suggested I 'keep an eye on him;' although he was not more specific. Weather at the time was IFR; ceilings approximately 700 AGL; with 1 SM visibility and light snow. Aircraft X checked on my frequency inbound. He was told to continue; vehicles on the runway. There was no readback. After he checked on; I noticed his altitude did not look right; so I referenced the approach plate and crosschecked his altitude at the FAF; the MSAW alert went off. Crossing altitude at the FAF was 5200'; the aircraft was at approximately 4500'. There was discussion among the controllers in the cab as to which altitude to give him; with the MDA suggested; although he was still outside the FAF. I thought it did not make much sense to give him the MDA; since that would descend him further (4040' MSL); but decided I had to give him something and told him to check altitude immediately and recommended he execute a missed approach. There was no readback. I tried to contact him again; using only his call sign and no message; and he did respond. When I issued the alert again with the climb recommendation; he read back 'climbing out.' He did appear to start a climb; up to 4600'; and then seemed to level off; so I inquired whether he was still on the approach. He replied that he was receiving a lot of static in the transmission; which is a known issue to the east of the airport. I instructed the snow removal vehicles to exit the runway at this point; not certain what his intentions were; and repeated my inquiry. He stated again that he had a lot of static and he wasn't catching my transmissions; then reported on the missed climbing through 4600'. I instructed him to proceed direct the VORTAC; which had been communicated via ARTS scratchpad to be his missed approach instruction. Three minutes later; after he was west of the airport and I could confirm his climbout; I transferred him back to departure. Recommendation; this was the first safety/terrain alert I had issued. I knew the phraseology from classroom and training; but had never had to use it and was stuck as to which altitude to give the pilot given his position on the approach. As a result; the phraseology came out incorrectly and did not sound as forceful as it should have. I had to issue another low altitude alert later in the evening; which sounded much more confident; and the pilot (different aircraft) responded appropriately. Additionally; although we cannot refuse a pilot a legal request; it was not advisable for this particular GA pilot being out practicing IFR approaches in actual IFR weather. I have not seen this aircraft practicing instrument approaches in VFR conditions; and it showed in his inability to hold altitude on the VOR DME Runway 28R approach; as well as his inability to track radials and perform published VOR holding patterns in subsequent approaches. He was practicing non-precision approaches for which the weather was barely at minimums or below minimums. In this situation; it was intimidating to be the controller who might have to talk him down in an emergency; seeing as he wouldn't legally be able to land on the approaches he was attempting.
During the training flight; instructor and student set up for the VOR/DME Runway 28R approach via the 16 mile Arc. Prior to beginning the approach; the incorrect identifier for the navigation facility was entered into the GPS unit as KBIL rather than BIL. The GPS as a result provided all DME distances to the airport rather than the VOR facility. As a result; aircraft descended approximately 4 miles prior to the published IAF 'MUSTY' when the aircraft was approximately 4 miles EAST of the IAF at that point. This early descent created extreme static on the radios in the aircraft preventing the Pilot and Instructor from hearing BIL Tower warn them of their early descent.The aircraft then performed the published Missed Approach procedures climbing to 6;000ft; and flying directly to the BIL VOR and entering into the holding pattern. Flight Instructor realized the Navigational Set-up error while holding over the VOR and recognized the distance displayed was incorrect as per the situation. Instructor and Pilot changed the identifier which had been input into the GPS from KBIL to the correct identifier of BIL to rectify the situation.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.