|
Post by bjratchf on Dec 20, 2013 17:21:46 GMT -5
I know that this "out off on in" information is available through the administrator, but I was wondering if you guys could make a page that records the block times in Zulu format.
After takeoff in real operations we often refer to it when making a delay report back to the company.
Simple out time could be when all doors are closed and the parking brake is released for the first time. Off is of course, takeoff time; on is landing, and IN is parked at the destination gate with the first door opening.
|
|
|
Post by Travis on Dec 20, 2013 17:57:36 GMT -5
That's something which we've discussed, and have targeted for a future build. But we've not settled on the precise format that would be most useful....
In which file would you rather have such recorded??? It's possible to update the current dispatch file... but those files are meant to be "human readable" rather than "machine/data readable".
I've even thought of an "after flight report" file which would mimic one of the earlier files (such as the dispatch form). But if your VA or other operation would rather have a separate "machine readable" text file, we could consider such. The biggest issues would be in the naming and contents of such a file.
Such would necessarily represent the best way to present such data to the largest audience....
|
|
|
Post by bjratchf on Dec 20, 2013 23:41:45 GMT -5
Hmmm I don't know, I run my own virtual company on air hauler, and simply record the stuff into a spreadsheet along with my squawks (which is how I combat FSX tweaks/problems, for my "maintenance day"). These addons are becoming so realistic you can track fuel usage and inefficiencies.
|
|