Air France 28 near miss at LAX: the unauthorized left turn into an American departure
An Air France A350 lifted off LAX's north inboard runway and turned left, toward an American A321 climbing off the south inboard runway. The departure controller turned the Air France jet west, stopped the American climb at 2,000 feet, and called traffic less than a mile ahead. Work the same kind of problem from a Southern California departure scope, and make the calls yourself.
What happened
In the first minutes of Saturday, November 7, 2026, at about 12:20 a.m. local time, Air France 28, an Airbus A350-900 bound for Papeete, Tahiti, departed Los Angeles International Airport from runway 24L and turned left, off its assigned departure path. American 1660, an Airbus A321 bound for Dallas-Fort Worth, was climbing out from the parallel runway 25R. The left turn pointed the Air France jet toward the American departure. The departure controller ordered Air France onto a west heading at once, issued a traffic alert to American 1660, and told that crew to maintain 2,000 feet. Both flights continued to their destinations. No injuries were reported. The FAA is investigating the event as a possible pilot deviation.
The FAA has not released an official closest-approach distance. Numbers circulating in news reports come from flight-tracking sites and are estimates, not an agency finding. They also do not all describe the same moment in the encounter.
| Date and time | Sat 7 Nov 2026, about 12:20 a.m. PST (08:20Z) |
|---|---|
| Airport | Los Angeles International (LAX), west flow, runways 24L and 25R |
| Aircraft 1 | Air France 28 (AF28 / AFR028) heavy, Airbus A350-900, registration F-HUVK, runway 24L, LAX to Papeete (PPT / NTAA) |
| Aircraft 2 | American 1660 (AA1660 / AAL1660), Airbus A321-200, registration N191UW, runway 25R, LAX to Dallas-Fort Worth (DFW) |
| Assigned departure | SUMMR TWO (SUMMR2), confirmed later on frequency by the Air France crew, according to published reports of the audio |
| Closest point | Not confirmed by the FAA. Tracking-site estimates vary; see How close did the planes get? |
| Controller | Departure controller. Several outlets published audio captured by ATC.com |
| Outcome | Immediate west heading for AF28, traffic alert and a 2,000-foot hold for AA1660, no injuries reported; possible pilot deviation. Both flights continued |
How parallel departures at LAX work
LAX has two pairs of runways: the north pair (24L / 24R) and the south pair (25L / 25R), with the terminals in between. When the airport is in west flow, jets take off toward the ocean. The inboard runways, 24L on the north side and 25R on the south side, are the ones used for these two departures, so the two climb-outs start closest to each other.
LAX launches off both sides at the same time. Two departures can roll almost side by side, so long as each jet stays on its own departure path. Early in the climb, nobody is separating them by altitude yet. The spreading paths are the separation.
Illustrative only. Runway positions are from FAA data; the dashed straight-out lines and the red turn are drawn to show the idea, not either aircraft's actual track, distance or timing. We have not exported or re-measured the ADS-B tracks for this event.
Air France 28 was off 24L, on the north side. American 1660 was off 25R, on the south side. Both were assigned a standard instrument departure, the published climb-out route known as the SUMMR TWO. Coverage of that procedure, including The Aviation Herald and Simple Flying, describes an initial climb straight ahead before the route continues west. A left turn off 24L points a north-side departure toward the south-side stream.
The same 24L / 25R pairing is in our Delta 958 near miss breakdown from April 19, 2026, when a Delta 767 off 24L turned left toward a SkyWest jet climbing off 25R. Another LAX incident on our site, the United 530 and United 152 close call, also involves runway 24L, on the ground rather than in the air.
The sequence, as reported
Exact radio times were not published in an official transcript. What follows is the order of events in contemporary coverage, not a second-by-second reconstruction. Local times are Pacific Standard Time.
About 12:15 a.m.Air France 28 departs runway 24L
Air France 28 departs runway 24L for Papeete, according to departure times published by Simple Flying and AeroCorner. The Aviation Herald, citing the flight, says the aircraft was instructed to follow the SUMMR TWO.
About 12:16 a.m., moments laterAmerican 1660 departs runway 25R
American 1660 departs runway 25R for Dallas-Fort Worth. CNN reported that the American jet was cleared to take off from the parallel runway shortly after the Air France turn had begun. Simple Flying lists the American departure a minute after Air France.
In the climbThe unexpected left turn
The Aviation Herald reports that Air France 28 was climbing through about 1,800 feet MSL out of 24L when it started an unexpected left turn. That is an Aviation Herald figure, not an FAA measurement.
The first fix"Fly heading 270 immediately"
In audio captured by ATC.com and quoted by CNN, Fox News, CBS Los Angeles, NBC Los Angeles, and others, the controller tells the Air France crew:
"Air France 028 heavy, fly heading 270 immediately."
Heading 270 is west. Some published transcripts include the word "of" ("fly heading of 270 immediately"). The instruction is the same: turn west now, away from the south complex. A heading of 270 is not a climb to 27,000 feet.
The traffic alert"Traffic 12 o'clock, less than a mile"
The controller then warns American 1660. Patch, the Los Angeles Herald, and Fox News quote the call as:
"Traffic alert, traffic 12 o'clock, less than a mile. Maintain 2,000."
"OK, we'll go back to 2,000."
Fox News quoted the American crew's reply. Holding at 2,000 feet keeps a vertical gap open while the Air France jet is turned away. "Less than a mile" is what the controller said on frequency. It is not a surveyed closest-approach distance.
Shortly before 12:18 a.m.The course correction on playback
Patch, reviewing a Flightradar24 playback, wrote that the Air France aircraft could be seen making a rightward course correction shortly before 12:18 a.m., with the American jet following behind. Patch noted that the playback is a visual reconstruction and does not independently establish precise separation or the exact timing of the radio calls.
After the jets were apart"What departure were you instructed by tower to fly?"
The controller pressed the Air France crew on the turn. CNN, Fox News, and Patch quote the first line; CBS Los Angeles and NBC Los Angeles quote the follow-up:
"You were instructed to climb via SID, not turn to a heading."
"I need an answer. What departure were you instructed by tower to fly?"
Fox News and other outlets quoted the crew asking for a moment ("Give me a minute") and the controller replying, "No problem." Published reports say the crew later confirmed it had been assigned the SUMMR TWO, but that the exchange did not establish why the jet had turned. CBS Los Angeles described the questioning as going on for close to 20 minutes without a clear explanation of the turn.
Possible pilot deviationThe phone number
After the conflict was resolved, the controller advised the Air France crew of a possible pilot deviation and gave them a phone number to call, according to The Aviation Herald, Patch, NBC Los Angeles, and others. That scripted notification is often called a Brasher warning. It is the controller's first report, not a finding of cause or fault.
To the American crewAn apology
CNN quoted the controller's apology:
"Sorry about that. That aircraft just turned in front of you. They were instructed they were on the right departure, but you know, pilot deviation."
Both flights continuedAir France's statement
Air France told KTLA, as reported by NBC Los Angeles, Patch, and Simple Flying, that the crew received a request from air traffic control shortly after takeoff to adjust the flight path and "immediately followed the instructions before continuing the flight." The airline said the aircraft landed normally in Papeete at 5:59 a.m. local time. As of the Monday, November 9–10 coverage, American Airlines had not issued a public comment in the outlets reviewed for this page.
Published transcripts of these calls vary slightly between outlets. We quote only short lines that the cited outlets published; we have not transcribed the full frequency by ear.
What is a traffic alert?
A traffic alert is one of the most urgent calls a radar controller makes. FAA Order JO 7110.65, paragraph 2-1-6, is the procedure for safety alerts, including warnings of unsafe proximity. The call is reserved for a real collision risk, and it comes with an instruction to fly immediately: a heading, a climb, a level-off, or some combination.
Here the controller did two things at once. The jet that had left its path, Air France 28, was given an immediate west heading. The jet that was still on its path, American 1660, was told about traffic at 12 o'clock, less than a mile, and told to stay at 2,000 feet. One call steers the turning aircraft away. The other keeps a vertical gap from closing while that turn takes effect.
Why the turn was dangerous
Side-by-side departures at LAX only work if both crews hold their line. The north and south inboard runways are close enough that a left turn off 24L, early in the climb, points one departure at the other.
Until the jets are on diverging routes or stacked by altitude, a controller's standard radar separation is 3 nautical miles laterally or 1,000 feet vertically. A traffic call of "less than a mile," and the tracking-site estimates discussed below, are both inside that lateral standard. Whether official separation was lost, and by how much, is a question for the FAA's review. This page does not treat any unofficial figure as a finding.
The FAA has not said whether either crew received an onboard traffic collision-avoidance (TCAS) alert or resolution advisory.
How close did the planes get?
The FAA has not confirmed a closest-approach distance. Treat every number below as an estimate from flight-tracking data or from a newsroom's review of that data, and note that some figures appear to describe different moments in the encounter.
- CNN, citing Flightradar24, reported the closest point as about 4,000 feet apart horizontally, with the aircraft within 1,000 feet of the same altitude.
- Patch, citing AIRLIVE, reported a horizontal gap of about 0.76 nautical miles (roughly 4,600 feet, or 0.87 statute miles). Patch also reported that at a different point, the jets were about 300 feet apart vertically while 1.6 nautical miles apart horizontally. Patch stated those figures are tracking estimates, not official measurements.
- ABC7 Los Angeles wrote that some flight-tracking sites reported about 400 feet vertically and 4,600 feet laterally.
- The Los Angeles Times, citing air traffic control audio and flight-tracking data it reviewed, reported the Air France flight came within 500 vertical feet of the American flight, and that the controller said the planes were within a mile of one another.
- AeroCorner, citing the Turbinetraveler post that published audio with a Flightradar24 replay, reported a vertical gap of about 400 feet. AeroCorner also noted that the only figure spoken on the frequency is the controller's "less than a mile."
Those estimates are not in conflict in one important way: they all describe a close encounter, and none of them is an FAA measurement. Horizontal figures around 4,000 to 4,600 feet are roughly two-thirds of a nautical mile to 0.76 nautical miles. Vertical figures in the coverage range from about 300 to 500 feet at some points, to "within 1,000 feet of the same altitude" in the Flightradar24 account cited by CNN. Because the jets were climbing and turning, the closest lateral point and the closest vertical point may not be the same instant.
We have not independently exported or re-measured the ADS-B tracks for this page.
What the FAA said
On Monday, November 9, the FAA provided a statement to Patch and to other outlets. Patch published this text and noted that the agency said its information was preliminary:
"The crew of Air France Flight 28 made an unauthorized turn after departing Los Angeles International Airport and went into the path of another aircraft that departed from a parallel runway. Air traffic control immediately issued corrective instructions to the Air France flight."
CNN published the second sentence of that statement as well, and reported that the FAA described the turn as unauthorized and to the south. The agency has not, in the coverage reviewed for this page, released a closest-approach number, a cause, or a statement on whether either aircraft received a collision-avoidance alert.
A possible pilot deviation means the controller believes a flight departed from its clearance or from an instruction. Under FAA Order JO 7110.65, paragraph 2-1-27, the controller notifies the crew and documents the event so Flight Standards can review it. Most events without damage are handled under the FAA's compliance program and can end in no action or in training. More serious cases can lead to action against a pilot's certificate. Crews often also file a NASA Aviation Safety Reporting System report. None of that is a prediction of what will happen in this review.
What this one teaches
Three controller instincts, and why they show up in the audio.
Turn the jet that left its line, immediately
"Fly heading 270 immediately" gives the off-course crew a heading to fly, not just a reminder of the departure they were supposed to be on. The heading points west, away from the parallel stream.
Stop the other climb if you need the vertical gap
A traffic alert plus "maintain 2,000" keeps American 1660 from climbing into the turning aircraft. The published audio has the American crew accepting that level-off.
Ask why only after the conflict is solved
The questions about the SID, and the possible-pilot-deviation notification, come after the jets are being steered apart. Separate first. Document second.
Try it from the departure scope.
SectorLive puts you at a real radar position in Southern California, with real runways, real procedures and live traffic, and AI controllers in every other seat. It runs in your browser, free.
- Keep jets 3 miles or 1,000 feet apart
- Climb departures and turn them onto their routes
- Hand them off cleanly to the next controller
Has this happened on that runway before?
News coverage of this event pointed to two earlier unexpected turns off runway 24L. Investigators have not, in any source reviewed here, linked the three events or named a common cause.
- On October 31, 2025, The Aviation Herald reported that ITA Airways 621, an A330-900 departing 24L for Rome, turned left toward American 4, an A321 departing 25R for New York. Controllers held the American jet at 1,500 feet and turned the ITA aircraft onto a heading of 270. Tracking data cited in that reporting put the jets about 0.6 nautical miles apart at the same altitude. That figure is also not an FAA finding in the materials we reviewed.
- On October 20, 2026, The Aviation Herald reported that TAP Air Portugal 248, an A330-900 bound for Lisbon, made an unexpected left turn after departing 24L. Patch and others noted that this event has not been established as a near-collision.
Those earlier events are context, not an explanation of November 7.
Air France 28 and American 1660 LAX near miss: common questions
How close did Air France 28 and American 1660 get?
The FAA has not published an official closest-approach distance. Flight-tracking estimates reported by news outlets range from about 4,000 to 4,600 feet horizontally (CNN, citing Flightradar24; Patch, citing AIRLIVE; ABC7). Vertical estimates in that coverage range from about 300 to 500 feet at some points, to within 1,000 feet of the same altitude in the Flightradar24 account cited by CNN. Patch noted that a 300-foot vertical figure was at a different point, when the jets were about 1.6 nautical miles apart. The only distance spoken on the frequency, in the published quotes, is the controller's traffic call of "less than a mile."
What did the Air France jet do wrong, according to the FAA?
The FAA said the crew of Air France 28 made an unauthorized turn after departing LAX and went into the path of another aircraft that had departed a parallel runway. Air traffic control "immediately issued corrective instructions." The agency said that information was preliminary. It has not said why the turn happened.
What is a possible pilot deviation?
It is the controller's notification that a flight appears to have gone against a clearance or an instruction. On frequency, it is typically paired with a phone number to call. That is a Brasher warning, not a verdict. The FAA reviews the radar data and the audio and decides what, if anything, follows.
Did the Air France crew say why they turned?
Not in the published coverage. Outlets that reviewed the audio say the crew confirmed they had been assigned the SUMMR TWO departure, asked for a minute when first pressed, and did not give a clear explanation of the turn. Air France later said the crew received a request from air traffic control to adjust the flight path and immediately followed it. The airline did not, in that statement, address why the jet had turned.
Was anyone hurt?
No injuries were reported. Both aircraft continued to their destinations. Air France said Flight 28 landed normally in Papeete at 5:59 a.m. local time.
Did either plane get a TCAS alert?
The FAA has not said. This page does not infer an onboard alert from the radio calls or from tracking estimates.
What departure were they supposed to fly?
Published reports of the audio say the Air France crew confirmed the SUMMR TWO, a standard instrument departure from LAX. Coverage of that procedure describes an initial climb straight ahead from the west-flow runways before the route continues. A left turn off 24L is not that initial track.
Where does Air France fly from LAX on Flight 28?
Air France 28 is the Los Angeles–Papeete service, operated in this case with an Airbus A350-900. The November 7 departure was the overnight flight to Tahiti, scheduled on November 6 and actually departing early on November 7, according to The Aviation Herald.
What happens next?
The FAA investigation was already open in the November 9–10 reporting. Typical next steps are a review of the radar and voice recordings and of the crews' accounts. There was no public, incident-specific FAA or NTSB report in the sources reviewed for this page as of November 17, 2026.
Sources
News reports, official statement, and flight data
- The Aviation Herald, "Incident: France A359 at Los Angeles on Nov 7th 2026, unexpected turn on initial departure", created November 8, 2026. Aircraft types and registrations, runways, the SUMMR TWO clearance, the unexpected left turn passing about 1,800 feet MSL, the heading-270 instruction, the 2,000-foot restriction on American 1660, and the possible-pilot-deviation phone number. This is a third-party incident report, not an FAA record.
- Patch, "Wrong Turn Puts Air France And American Airlines Jets On Collision Course Over LAX", November 9, 2026. The FAA statement, provided directly to Patch, with the agency's preliminary caveat; quoted radio; AIRLIVE tracking estimates; Flightradar24 playback notes; the ITA and TAP context; and Air France's statement to KTLA.
- CNN, "Close call at LAX airport as plane turns in front of another aircraft taking off", November 9, 2026. FAA wording, ATC.com audio quotes, the controller's apology to American 1660, and Flightradar24's reported closest-point estimate.
- Los Angeles Times, "Two planes nearly collide at LAX, FAA says", November 10, 2026. FAA statement and the Times' own review of audio and tracking data, including a 500-foot vertical estimate.
- CBS Los Angeles, "FAA investigating near mid-air collision at LAX between Air France and American Airlines flights". Time of about 12:20 a.m., radio quotes, and CBS's description of the later questioning.
- NBC Los Angeles, "Unauthorized turn placed Air France jet in path of plane at LAX", November 9–10, 2026. FAA wording, radio quotes, Air France's statement, and an NBC News vertical estimate of 300 to 400 feet.
- ABC7 Los Angeles, "Air France flight nearly hits American Airlines plane after taking off from LAX", November 10, 2026. Time of about 12:20 a.m., Air France's statement, and flight-tracking estimates of about 400 feet vertically and 4,600 feet laterally.
- Simple Flying, "Air France A350 Nearly Collides Midair With American A321 After Wrong Turn At LAX", November 8–9, 2026. Aircraft, registrations, reported departure times, the SUMMR TWO description, and the full Air France statement.
- The Los Angeles Herald, "Air France Jet's Unauthorized Turn at LAX Put It in the Path of an American Airlines Flight, FAA Says", November 10, 2026. A roundup of the FAA statement, radio quotes, and the tracking estimates.
- Fox News, "An American Airlines plane and an Air France jet nearly collided at LAX recently", November 10, 2026. FAA statement to Fox News Digital and additional audio quotes, including the American crew's 2,000-foot readback.
- AeroCorner, "Air France AF28 Turned Left After Takeoff From LAX, Toward an American A321 Climbing Off the Next Runway", November 8, 2026. Early account of the Turbinetraveler audio and Flightradar24 replay, with both aircraft reported airborne around 08:16 UTC.
- FlightAware history for AFR28 on November 7, 2026, linked from The Aviation Herald. This is a flight-history page, not an official separation finding, and it may not remain a permanent archive of the track.
KTLA reported the story on air, and several outlets attribute Air France's statement to comments made to KTLA. A lasting ktla.com article URL was not verified for this page. A third-party YouTube reconstruction of the audio is at youtube.com/watch?v=xjZK4sjGCxo. CNN and others cite ATC.com as the recorder of the radio audio. No LiveATC archive permalink was found. These recordings and reconstructions are third-party publications, not FAA releases. Transmissions quoted above may differ slightly from the audio.
Primary FAA procedure references
- FAA Order JO 7110.65, paragraph 2-1-6: Safety Alert. Phraseology and instructions for traffic alerts and immediate corrective action.
- FAA Order JO 7110.65, paragraph 2-1-27: Possible Pilot Deviation Notification. The prescribed notification, often called a Brasher warning.
- FAA Compliance Program. General background on how the FAA may address safety concerns. Not a statement about these crews.
These FAA links explain procedures. They are not incident investigation records. We have not verified an incident-specific FAA report or NTSB investigation record for this encounter as of November 17, 2026. This page is an educational summary of published reporting, not an official finding of cause, fault, or separation. The runway diagram is our own illustration, not a reconstruction of the flight tracks.