Time Zone Functionality for Flight Data in Flight Log Book

Currently, the departure time and arrival time are assumed by the system to be converted to system time by the user when they are being entered in the Flight Log Book.  This singular functionality is a departure from the universal functionality of all other dates (status dates, meter reading dates, etc.)  throughout the application.  All other dates are entered by the user in their own time zone (as denoted in their user profile) then "on save" they are automatically converted by the application to system time to save in the database. This functionality ensures that all dates in the database are consistent throughout.   Furthermore, throughout the application except for the flight data, the user interface defaults the dates displayed to the user in the user interface based on the user's time zone.  The deviant behavior of the flight hours meter causes miscalculations in flight hours used in preventative maintenance and work management by introducing database dates that are not in the system's time zone, so when compared to and used in calculations with other dates like work order completion date--it's not an equitable comparison.  

I propose that the Flight Log Book flight data functionality be brought in line with the functionality of the rest of the application.  To do so, two functions would need to occur:  

1.) Allow users to indicate what time zone the flight departure time and arrival time are being entered.  The time zones will be defaulted based on the user's time zone, if no time zone specified on the user's profile then default to system's time zone.   The departure time and arrival time will have their own time zone fields as they can be entered in different time zones.  These time zones will be used in the calculation to display the departure and arrival times in the user interface for the flight data.  The departure and arrival time zone should also be editable if the user selects "Edit History Flight Data". 

2.) On save, the time zone fields will be used to convert the arrival and departure dates to system time.  This way the date time zone, system time, stays consistent throughout the application and all calculations will be like comparisons.