Two pilots and an ATL TRACON Controller reported averting an airborne conflict after the pilots departed Runway 27 assigned a pre-takeoff 270 degree heading but thought they were to fly a JCKTS 5 RNAV and turned into Runway 28 departures.

2011-06 · NASA ASRS report 956428

Date: 2011-06 · Aircraft: Large Transport; Low Wing; 2 Turbojet Eng · Phase: takeoff

Anomalies: atc-issue-all-types|conflict-airborne-conflict|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance

Synopsis

Two pilots and an ATL TRACON Controller reported averting an airborne conflict after the pilots departed Runway 27 assigned a pre-takeoff 270 degree heading but thought they were to fly a JCKTS 5 RNAV and turned into Runway 28 departures.

Narrative

I was the pilot flying. ATC had issued us 'Line up and wait 27R' instructions. Prior to takeoff; ATC issued us a takeoff clearance which we had thought of as the JCKTS 5 RNAV departure. The Captain had transferred aircraft control to me for takeoff and had read back the ATC takeoff clearance. After departure; at 400 FT I had stated 'Set Nav' and Captain had selected the NAV button on the MCP. As I was initiating a gradual left turn to the first RNAV fix; ATC stated 'Confirm heading 270.' Upon hearing that statement; I immediately began to initiate a turn back to the right to establish the aircraft on a 270 degree heading and called for 'Set Heading 270.' ATC pointed out traffic to us which was off to our left at approximately the 8 o'clock position. I had no visual contact with reported traffic; however it was depicted to us on TCAS. There were no TCAS alerts (NO TRAFFIC ADVISORIES or RA's were set off) throughout the takeoff and climb out. After re-establishing the aircraft on a 270 degree heading and confirming the heading instruction given by ATC; we were handed off to ATL Departure Control and normal procedures and climb out took place. ATC did not comment any further in regard to the potential lateral or heading deviation. It was never stated that there was any separation issue. So; we continued without any questioning on our part. As a result of this event; I learned it is vital to ensure that a takeoff clearance is clearly understood by both pilots; and one must listen very carefully to any clearance which may be amended or altered in any fashion. It is true that my Captain and I were both convinced that we heard an RNAV takeoff clearance as opposed to a 270 degree heading to fly after departure. However I also realize that it's certainly possible that complacency may have been a potential factor; in that we were 'expecting' to hear a typical RNAV departure clearance instead of a 270 degree takeoff clearance. I am proud of the fact that I acted quickly and without hesitation by returning the aircraft back to the 270 degree heading and having my Captain verify the heading assignment with ATC. Our quick action and teamwork helped ensure that safety and separation standards were still met. We did not worry about who was right; but reacted to the situation and simply did 'what was right.'

Second reporter narrative

A takeoff clearance was received from ATC. Both flight crew believed and still believe the clearance was issued for the RNAV departure; as filed in the flight plan; and as was expected by the crew. The First Officer was the pilot flying; and normal procedures and call-outs were used. At 400 FT the First Officer called for 'NAV' and 'NAV' was engaged. As per the departure; the intercept to the course did not occur until about 2;100 FT; and at that time the FMS commanded a turn approximately 20 degrees to the left to intercept the RNAV course. As the aircraft rolled into the turn; ATC queried us; and asked us to verify that we were on a 270 degree heading. We immediately rolled the aircraft back to the right and verified that the Controller now wanted us on an assigned heading. Shortly thereafter the Controller issued a 280 degree heading. We complied with his instructions and the flight proceeded without further incident. Evidently the Controller believed that the takeoff clearance issued included an assigned heading; and the flight crew believed that we were issued and RNAV departure clearance.

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.