¿Have you need to reject the takeoff?

Hi guys! I watched too much questions about stop a takeoff, and in this simulator doesn’t exist any kind of command for this, so the questions is:
Is really necessary stop a takeoff?

I’ve only seen a handful topics on takeoff cancellation.

And since IF is a simulator, with pretty good flying characteristics, it can be useful or even necessary to cancel a takeoff, yes. If your aircraft is too heavy and you forgot to set your flaps, you need to abort and try again.

A takeoff abort doesn’t always have to be pilot initiated. Tower could do this as well.


Lets just say you forget to set flaps or forget to start your second engine, or forget to calibrate your device, yes this is necessary.

If you want to vote for this command check this out :)


I can give you a few scenarios in which you may need to cancel takeoff:

Pilot Initiated:

  • Forgot to turn engine on
  • Do not feel comfortable with runway remaining
  • Do not feel comfortable with weather/takeoff conditions
  • Forget to lower proper flaps amount

Controller Initiated:

  • Traffic enters runway without permission
  • Aircraft on final executes go around. Cancel takeoff is called to avoid a conflict with departing aircraft and G/A aircraft

Hope this helps


I don’t know if this is too off topic, but what if you’re already at a high speed and you can’t tell the aircraft to cancel takeoff clearance what are you supposed to do

1 Like

Well yes, over a certain speed we obviously would not cancel the clearance :)

1 Like

In really, this is a good question.
I think we need to takeoff and do a patern.

1 Like

So how are you meant to deal with the conflict as a controller then?

1 Like

Wow! I dont have any response to this.

1 Like

If that happens, I’ll normally just send the go around aircraft a traffic alert and then hand them to approach.

1 Like

Anyway i think the controller NEVER need to ghost.

There will always be a need for ghost. Especially if a pilot is being unrealistic and interfering with traffic.
And it’s not a punishment it’s a learning experience.

1 Like

There was one time I was ready do a flight, double checked everything thought everything was good to go. Perfect engines on taxi to take off. On my initial roll I failed to add the correct fuel my finger slipped and I accidentally added less fuel then I required.
So cancel take off taxi off runway redo that issue then I continued on with my flight landing with my fuel I needed

1 Like

So I have a question. Let’s say, on expert server, tower gives you clearance for takeoff, and you start rolling down the runway and all of a sudden… (now this might be un realistic in expert server)… someone crosses the runway and ignores ATC completely, which forces us to abort takeoff. What if the ATC never saw that other aircraft crossing the runway and we suddenly stopped and turned onto the taxiway. Do we say, “I’m sorry” to ATC because there is no abort takeoff command for the pilots? ATC would not ghost us right? You never know which types of ATC people are there and how they respond so thats why


My criteria for a Rejected takeoff are the following:
Lined Up, idle thrust

  • Weather, flaps, trim, calibration, fuel, conflicting traffic, basically anything that would impede the safety of the flight.
    >80 knots
  • flaps, trim, calibration, an “off” engine, spoilers extended, traffic
    > V1
    Traffic, or engine/control issue

When you forget to turn on a engine.

To my understanding after V1 you are committed to the takeoff but I’ll let the experts explain it if I’m incorrect… I’ve seen episodes of air crash investigation or May Day where the pilot was beyond V1 and still had to lift the aircraft


Adding: It might be necessary to abort a takeoff if a go-around happens on a runway which’s go around path is crossing your departure runway/path.

For example in Zurich if RWY10 is in operation and an aircraft on RWY14 performs a go-around you’d have to abort the takeoff.


The crossing traffic would be ghosted if they were never cleared to cross, and if they received clearance, then probably an IFC PM with all the controllers.
ATC has absolutely no right to ghost the pilot on takeoff if they aborted and cleared the runway. If they continued, in my opinion that should be addressed with a PM after the flight.
It is a pilots job to ensure the runway is clear before entering it, and it is the duty of a controller to make sure the runway is clear before allowing anyone to enter.
The bottom line is, if you reject for a real reason, and don’t cause any there is no reason to face repercussions


@Ulises25. MaxSez: The accepted term is “Rejected” Take Off” not “Aborted”!
IF aircraft are not programmed to have mechanical malfunctions thus there are no commands or requests for a “Rejection” in the IF Communication Menu or Lexicon. Pilots who attempted to initiate a Rejected Take Off action, stopping on the rway on the roll, in most cases would be Ghosted since there is no reasonable excuse for this action except Pilot Error. Failure to deploy Flaps is a Pilot Error, a Rway incursion is a Pilot Error on the part of the aircraft that entered the RWay. w/o permission. Incursion on a take off roll; if clear continue the launch IF ABLE or await ATC instructions at full stop.
(RW. V-1 is not , strictly-speaking, the maximum rejection speed. It is the maximum rejection speed for the specific case of a single engine failure during takeoff with no other damage resulting . There are plenty of failures that would require rejecting a takeoff even after V-1 (for instance, [an elevator failure]. Tower would be advised by the PIC of the rejection. If Able Tower would advise Taxi Clear with a switch to Ground for Exit/Taxiway guidance.)
Just Sayin, Max