On the morning of 15 September 2026, flight TK30 from Newark to Istanbul hit the ground at EWR and I was launching the runway without permission for the Turkish Airlines Airbus A350-900. If it sounds like a bad idea, it was, but not as bad as it might seem.

It happened this way, it was the fault of such-and-such and it was important for this reason and that reason and this reason.

What happened on Flight TK30?

Turkish Airlines (TK) flight 30, an Airbus A350-900 was preparing to take off from Newark (EWR) for Istanbul (IST). During its taxi, the plane unilaterally took off onto runway 4L. That seems like a risky idea but the events actually unfold in a much more complicated manner.

The night was quiet and there was no risk of collision due to the lack of other aircraft in the area. Nevertheless, it's a serious offense to not clear a runway and that was the reason for the crew to be given a phone number to call in case there was a pilot deviation.

Why the friendship turned sour

The trading commenced as usual.The trading started off regularly. The crew from Turkey requested a taxi and the controller instructed them to taxi runway 4L for departure through taxiway B. It was read back correctly by the pilots. So far, so good.

Then the controller stated that the aircraft would be next and requested that the crew notify the controller when they were ready to depart. The controllers then gave a go to the pilots and they replied, ‘Roger, thank you.

After a lapse of about 50 seconds. The aircraft was not yet at the hold short position but was soon approaching the taxiway to the runway. However, seeing this, the controller questioned if the crew could proceed for the runway. The pilots agreed and the controller responded, “Okay, proceed on to the runway.”

‘That' is the centre of the story. The pilots seem to have thought, “Okay, let's get in line.The pilots seem to have interpreted this as “Okay, let's get in line.” They taxied on to runway 4L and stopped. The controller yelled at them when they called and they said 30 seconds, they said, because of a slight technical problem. Then the controller directed them if they knew they were on the runway and they told him that they were not cleared onto the runway.

Where the Pilots Went Wrong

Let's have a discussion about who's responsible. Pilots should not be allowed to walk onto runways in the United States without specific clearance to line up and wait or to take off. Here that was not done. Regardless of all that, the crew should have stopped at the hold short line and confirmed.

Pilots are prepared for just such a situation. If the instructions are not clear, don't assume, ask. If the crew had asked the controller, it would have been a non-event.

The Controller's Wording was lacking in places.

Simultaneously, it's clear that there was a mix-up, and no wonder. The sequence was: The controller requested the crew to advise if they were ready, the crew responded that they were ready, and then the controller said “continue for the runway.” When a pilot is expecting the next command to be "takeoff" or "line-up," the line seems to be a green light.

There was a better way. There wouldn't have been any doubt about it with something like “continue your taxi” or “continue your taxi, hold short of runway 4L”. It is not about faulting but establishing a framework where miscommunication is not likely to start.The Case for Standard Phraseology is a booklet that explains why standard phraseology is necessary.

The majority of the world uses uniform phrases for communication between the controller and the pilot. The crews are from various countries and native tongues, so it is only natural. The fewer ways to say something, the less the chance that it will be misunderstood.

This is a more relaxed place in the United States. Controllers tend to use plain, conversational language that may appear natural, but can be prone to ambiguity. This wasn’t a one-off, either. A Qatar Airways Cargo Boeing 777 taxied onto a runway at Houston (IAH) earlier this year due to confusion over the word "Cargo".

If the error is occurring repeatedly, it might be a system issue and is worthwhile to ask if the system is the problem. Strict standards are not meant to penalize anyone. They're in the business of taking guesswork out of the equation, when guesswork has no business.

Key Takeaways

• In the U.S. pilots are never to be cleared to enter a runway without permission.
• There is no clearance to line up and take off to “continue for the runway”.
• When instructions are unclear, always ask, never assume.
• The use of standard phraseology minimises the risk of expensive miscommunications.

The Bottom Line

A Turkish Airlines A350, which had been towed onto one of Newark's runways without permission, should be blamed on its airlines' pilots. The vague language used by the controller, however, was undoubtedly a factor, and the incident in Houston earlier this year was no exception.

Luckily there were no fatalities or other vehicles involved. What the lesson is: that language is the key to saving lives, and that standardizing U.S. air traffic control with international standards would be a good way to avoid another near-miss.