Peter Schindler
Founder
- Users Local time
- Today 4:42 PM
Today I fixed a couple of reports, especially with wrong or missing distances and flight times. It's something I do regularly, and I don't mind doing it, since it doesn't happen too often.
Recently there have been more "buggy" reports, though. That's why I would like to remind you (especially all new pilots) to follow some basic advice with flight reporting. Especially when using FsAcars and XAcars (the other 2 tools proved very stable, so far):
- Please make your flight briefing and booking as complete as possible. If you book a charter flight, follow the briefing and insert your flight plan (DEP - waypoints - ARR), whenever possible.
- After you have started up your FS and pirep add-on, please get the data from your booking via the appropriate buttons:
XAcars -> "Get ACARS Flightdata"
FsAcars -> "Get flight from VA"
many problems only arise because of missing data, like flight number and/or aircraft registration number.
Fetching the VA briefing data is the easiest and most secure way to make sure everything's in place.
- Avoid time or space shifting after you've started your pirep add-on. Make your complete aircraft setup first, including fuel and payload. Only start the pirep add-on when you are ready for startup/pushback, parking brake still set.
- on arrival, taxi to the stand, set brakes, shut down engines - then stop your flight logging and transmit your pirep before you do anything else.
It's also a good idea to disable crash detection, in case you crash into AI traffic or scenery. If it happens after arrival, you will be warped back to departure - something that pirep tools don't like at all
If you have any questions regarding your reports, don't hesitate to post them here.
And of course we recommend reading the pilot manual.
:fly:
Peter
ps: I sent a mail to the XAcars team today, about the problem with total distance recording and asking them to include the distance parameter in one of the next versions, so we do not have to use workarounds anymore. I'll keep you updated.
Recently there have been more "buggy" reports, though. That's why I would like to remind you (especially all new pilots) to follow some basic advice with flight reporting. Especially when using FsAcars and XAcars (the other 2 tools proved very stable, so far):
- Please make your flight briefing and booking as complete as possible. If you book a charter flight, follow the briefing and insert your flight plan (DEP - waypoints - ARR), whenever possible.
- After you have started up your FS and pirep add-on, please get the data from your booking via the appropriate buttons:
XAcars -> "Get ACARS Flightdata"
FsAcars -> "Get flight from VA"
many problems only arise because of missing data, like flight number and/or aircraft registration number.
Fetching the VA briefing data is the easiest and most secure way to make sure everything's in place.
- Avoid time or space shifting after you've started your pirep add-on. Make your complete aircraft setup first, including fuel and payload. Only start the pirep add-on when you are ready for startup/pushback, parking brake still set.
- on arrival, taxi to the stand, set brakes, shut down engines - then stop your flight logging and transmit your pirep before you do anything else.
It's also a good idea to disable crash detection, in case you crash into AI traffic or scenery. If it happens after arrival, you will be warped back to departure - something that pirep tools don't like at all
If you have any questions regarding your reports, don't hesitate to post them here.
And of course we recommend reading the pilot manual.
:fly:
Peter
ps: I sent a mail to the XAcars team today, about the problem with total distance recording and asking them to include the distance parameter in one of the next versions, so we do not have to use workarounds anymore. I'll keep you updated.