You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Foreflight import should support tail number as an optional column for easier sim import, should map out/in to block instead of engine, add TimeOff TimeOn for flight times
#1308
Closed
ericberman opened this issue
Sep 15, 2024
· 1 comment
E.g., you could put the "SIMxxxx" tail numbers in and have them import correctly.
ericberman
changed the title
Foreflight import should support tail number as an optional column for easier sim import
Foreflight import should support tail number as an optional column for easier sim import, should map out/in to block instead of engine
Sep 17, 2024
ericberman
changed the title
Foreflight import should support tail number as an optional column for easier sim import, should map out/in to block instead of engine
Foreflight import should support tail number as an optional column for easier sim import, should map out/in to block instead of engine, add TimeOff TimeOn for flight times
Sep 17, 2024
- Add TailNum as a synonym for AircraftID
- Map out/in to block time instead of engine.
- Map on/off to flight start/stop
- Move three static regex expressions into lazy-load RegexUtility
No description provided.
The text was updated successfully, but these errors were encountered: