SF340 Captain reports communications breakdown with ATC during approach causing altitude deviations both leaving assigned altitude and attempting to return to it.

2008-12 · NASA ASRS report 817200

Date: 2008-12 · Aircraft: SF 340B · Phase: approach

Anomalies: aircraft-equipment-problem-less-severe|deviation-altitude-excursion-from-assigned-altitude|deviation-altitude-overshoot|deviation-discrepancy-procedural-clearance

Synopsis

SF340 Captain reports communications breakdown with ATC during approach causing altitude deviations both leaving assigned altitude and attempting to return to it.

Narrative

The aircraft was established in a descent to 5;000 FT; our clearance was 'Pilot's Discretion to 5;000 FT.' As the aircraft descended; the Controller asked what approach we would like. The weather (330 degrees at 5 KTS; 9 SM visibility; broken 7000 FT) suggested that a visual approach was possible. We were still in IMC at about 5;800 FT so the First Officer and I reasoned that the visual was not such a good idea because the weather was not as the ASOS described. We decided that the ILS 35 was in order. I asked for the ILS approach and the Controller told us to expect vectors. After a brief pause; the Controller said 'radar contact lost.' There was not an audible call sign given and I assumed that he was still talking to us. He followed with 'you can fly the ILS on your own at 5;000 FT or climb to 6;000 FT for vectors;' we asked for the vectors/climb. The Controller said 'climb/maintain 6;000 FT vectors for the approach.' The altitude alerter was set to 6;000 FT and a climb was initiated. The Controller then gave a heading. The Controller then said 'aircraft X climb to 6;000 FT for vectors.' At that time we realized that the Controller was talking to someone else. We corrected the altitude alerter and initiated a descent to 5;000 FT. At 4;800 FT the First Officer and I noticed the altitude deviation and shortly thereafter the Controller questioned our altitude; due to the fact that the ALTS didn't capture. A correction was initiated but not fast enough; the aircraft continued in a descent. The autopilot was deactivated and a manual recovery was started. The aircraft captured 5;000 FT and the flight to ZZZ and the subsequent flight ZZZ1 continued unimpeded. This event happened because of changing weather conditions; both pilots selecting approach plates at the same time and the omission of inaudible call sign leading to conflict of instructions. Incidentally; the actual weather was broken 4;300 FT and 6 miles visibility.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.