Skip to content
  • There are no suggestions because the search field is empty.

18 - 19 November 2026 | Upcoming Release: Post-flight day/night calculation improvement (v2026.3.42)

This release improves how FL3XX classifies takeoffs and landings as day or night when a post-flight is saved.


Made for:  

Category:


Subcategory:

Web app tag

 

Crew - feature category tag

Included in: All subscription tiers Knowledge Base:  

 

1. About the improvements

    1.1 What to keep in mind

2. Why this will change

3. Some benefits at a glance

4. FAQs

    4.1 Do the night recency rules change?

    4.2 Will my pilots' status change on release day?

    4.3 Will my existing post-flights be corrected?

    4.4 Are we affected?

    4.5 We use the Manual setting. Does this affect us?

    4.6 Does this affect FRAT?

    4.7 Will data we've sent to integration partners change?

 


1. About the improvements

  • Day/night now follows only your day/night calculation setting.
    With the US setting, night is 1 hour after sunset to 1 hour before sunrise. With the EU setting, night is from the end of evening civil twilight to the beginning of morning civil twilight.
    Before, operators whose date-format setting didn't match their day/night setting could get the wrong result near sunset and sunrise.
  • The first officer's landing is now classified by its own landing time.
    Takeoffs by additional crew, flight attendants and onboard engineers are now also classified by their own time. Before, it took the takeoff's result.
  • High-latitude fix.
    At some airports in summer, takeoffs and landings in the middle of the day could be classified as night. This is fixed.
  • Flights with more than one landing count as night only if both the takeoff and the landing are at night.
    The commander already worked this way; the FO and crew now do too.
1.1 What to keep in mind
  • The night recency rules are not changing.
  • Only counts FL3XX calculates automatically are affected (Crew App and External API). Values entered in the web post-flight form, and operators using the Manual setting, are not affected.
  • The fix applies to post-flights saved after the release of v2026.3.42. Existing post-flights keep their current values, so pilots' recency status doesn't change on release day. If your existing records are affected, our team will contact you before anything is corrected.
  • If you edit the takeoff or landing count on an existing post-flight in the Crew App, it's recalculated using the corrected rules.
  • The FRAT "Night Operations" item uses the same setting, based on the on-block time at the destination. Operators whose date format doesn't match their day/night setting, and operators at high latitudes in summer, may see it trigger differently than before.

 


2. Why this will change

We found errors in how night takeoffs and landings were classified. Night counts feed recency (the 90-day night items, the 6-month turbine night item and the Part 142 night item), so some pilots could show as current or not current incorrectly. This is now fixed.

 


3. Some benefits at a glance

  • Night takeoffs and landings are classified consistently, using the night definition you've selected.
  • First officers' night landings count correctly toward their recency.
  • Recency and FRAT Night Operations reflect when flights actually happened.
  • ...and more!

 


4. FAQs

4.1 Do the night recency rules change?
No. Only the classification is corrected.

4.2 Will my pilots' status change on release day?
No. Existing records keep their values. New post-flights are classified correctly from the release (v2026.3.42) on.

4.3 Will my existing post-flights be corrected?
Not automatically. If your records are affected, we'll contact you before anything changes.

4.4 Are we affected?
Only if your counts come from the Crew App or External API. The date-format problem only affected operators whose date-format setting didn't match their day/night setting. The first-officer fix applies to everyone using automatic counts.

4.5 We use the Manual setting. Does this affect us?
No.

4.6 Does this affect FRAT?
Yes, the Night Operations item. See above in 1.1 What to keep in mind.

4.7 Will data we've sent to integration partners change?
Not with this release. If existing records are corrected later, we'll let you know first, because partners may hold the old values.