"Airline Procedure" what excatly does it take into consideration?

I have got it even worse yesterday. After accepting a B737 passenger transport mission and hitting fly, the aircraft loaded into the parking lot with the entered prohibited airspace error.

May be AI is writing the code instead of actual people, causing these type of weird errors.

I don’t think it’s just about missed ATC calls, because in this screenshot you can clearly see that I missed one due to a new bug introduced with SU2, where part of the runway is mistakenly recognized as a taxiway when approaching the blue exit markers

And yet, I still got my 100%. What I do is follow the checklist, comply with radio communications (except on landing, that bug has been permanent since SU2), stick to proper flight procedures, and I almost always end up with a 100% score.

Airline Procedures: 1. Don’t ask for lower flight level than assigned.
2. Accept the revised approach and runway it gives and follow that. Dont ask for runway changes approach proc changes etc
3. dont cross the 250k barrier.
4. Dont Stall and on landing use spoilers and reverse thrusters first then apply brake at 60K and flaps overspeed is a no no!
5. lights during nights and at the start keep all types of lights on.
These 5 params count the maximum.

Passenger satisfaction: I have no clue what determines that. I do all announcements, give them food, dont lose their luggage yet I never get 100%

Aviator performance: Taxi speed, flaps overspeed, taxiways etc all count.

I just got my first 100% airline procedures and I don’t know how
.

It’s crazy though I’ll have a real bad flight, but somehow my reputation will go up but then I’ll have a great fight which nothing went wrong and I’ll lose a whole reputation grade. It does not make any sense whatsoever.

100% “airline procedure”

After a lot of digging, here is what I believe goes into Passenger Satisfaction:

  • clean aircraft
  • g-forces kept between 0.7 to 1.5g
  • bank angle <20°
  • pitch angle <15°
  • five announcement bonuses (welcome, takeoff, cruise, descent, landing)
  • on-time meal service (starts 1/4 through flight)
  • landing:
    • don’t bounce
    • vertical speed closer to 75fpm to the normal (NOT raw vertical speed)
    • indicated airspeed at touchdown near 1.2 x VS0).

If you install the SDK samples you can find ‘simvar watcher’ tool and use that to observe some of these factors. It is way too easy to exceed 1.5g – so easy that I suspect the computation of g-forces is bugged.