2011-11 · NASA ASRS report 978110
B737-700 flight crew reports distractions and omissions during descent on the HONIE arrival into ATL resulting in descent below assigned altitude. ACARS ATIS update function had retrieved information from the departure airport; which resulted in an incorrect altimeter setting; and a conversation with the Jumpseater delayed completion of the Descent Checklist.
During descent on the HONIE arrival into ATL; the Captain and I were involved in a conversation with a pilot on the jumpseat. While in contact with Atlanta Center; we were descending to FL210. We were cleared to cross HONIE at 14;000' and 250 kts. I am fairly sure that the Atlanta Center Controller did not issue an altimeter setting for Atlanta; as I believe it is their policy to do. However; because I was engrossed in conversation with the jumpseater; I didn't query ATC on the matter. I simply read back the clearance; confirmed that the Captain (PF) set the MCP and FMC correctly; then returned to our conversation with the jumpseating pilot. Also around this time; the ACARS alerted us to a new ATL arrival ATIS. I selected the ACARS on the MCDU; glanced at the new ATIS; noted the altimeter setting of 30.26; and preset my altimeter setting to 30.26. I also printed the ATIS; but did not retrieve it from the ACARS printer. Upon passing through FL180; I set my altimeter setting to 30.26; and I believe the Captain did the same thing. Instead of running the Descent Checklist; the Captain and I returned to the conversation with the jumpseater. We were handed off to ATL Approach; who cleared us to descend to 11;000'. The Captain set 11;000' in the MCP and started the descent; and I verbally confirmed the same. As our altitude approached 11;000; we got one; then two TCAS TA's on traffic which appeared to be at 10;300'. When we leveled at what we thought was 11;000'; we noticed that both TCAS targets were now 700' below us. We both started to mention to each other that the situation didn't look right; but were interrupted by the Atlanta approach controller saying 'maintain 11;000'. I replied; and he again repeated the clearance; along with something along the lines of 'check your altitude'. I asked for the altimeter setting; and he read back '29.88'. At this point; the Captain had disengaged the autopilot and begun to climb. I reset my altimeter; then his; to 29.88. It was evident at this point that we were a little more than 300' low. The Captain flew the aircraft back to 11;000' and then asked me to re-engage the autopilot. I then retrieved the ATIS printout from the printer; and read it. For some reason; the ACARS had been delivering the (departure airport) ATIS to us the whole time; instead of the ATL ATIS. I realized that I failed to read the header line of the ATIS carefully; and did not notice the aberrant behavior of the ACARS ATIS function. The Captain then called for the Descent Checklist; which we completed.THREATS: ongoing non-pertinent conversation in the flight deck (which we did conclude by 10;000'); failure of ATC to provide altimeter setting; aberrant ACARS behavior. ERRORS: failure to complete Descent Checklist at appropriate time; failure to read ATIS display/printout carefully. Sometimes; going sterile at 10;000' isn't enough. Switching to any approach control marks the beginning of a busy phase of flight; and consideration should be given to extending sterile cockpit from 10;000' to whenever we switch to approach control.
I was the flying pilot on this leg. During the descent from cruise altitude my First Officer; the jump-seater and myself were involved in a conversation. We retrieved the ATIS electronically and we setup for ILS PRM 28 approach. Prior to FL180; I briefed the approach to the First Officer. I did not brief the altimeter setting. Through FL180 I set up the altimeter based on the First Officer side of his display. That was the first error; not setting the altimeter setting from the ATIS printout. Second error in the chain of events was that I failed to ask for the descent checklist passing through FL180. Our final descent altitude was 11;000. I leveled off and soon after a TA was issued on the NAV display. A second airplane appeared and both were 700 FT below us. I realized it must be our altimeter setting and asked the First Officer to verify altimeter setting with ATC. At the same time ATC asked to level at 11;000 and check our altitude. I disconnected the autopilot and climbed 300 FT and set the new altimeter setting. The flight proceeded with no further incidents.
No new information was obtained from the reporter during the Callback conversation.
More incidents for this aircraft family
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.