Pirep Correction

Here is where the coffee machine and Coke machine are kept. Please clean up after yourself and do not remove the magazines from this area. A good place to exchange thoughts with Operations personel and other pilots.

Moderators: Staff, HR, Flight Ops

Post Reply
Greg Goodavish
www.meble-kuchenne.warszawa.pl

Pirep Correction

Post by Greg Goodavish »

UGHHHH! I did it once again. When I selected a flight in FS to get the PMDG 744, and then moved it to RKSI, it set my FS date as 8-01-05, and I didn't notice it. Therefore, my December flight from RKSI to VHHH is showing up as being done on 8-1-05, instead of the correct date of 12-18-07 (simulator date. I had to fly it today, 12-17-07, as I have something going on the actual real date). Could someone correct that for me? Also, I am still getting all of those annoying error messages that I posted about before when I first start up GCP, even though I have flown several flights with it now since the latest update. Anyone know how to get rid of those? An annoyance only, as the GCP utility records the flight fine. Thanks. :)
hawkeyeted

Post by hawkeyeted »

Greg,

Did you try downloading the aircraft/flights via the "dowload" radio button? That fixed the error messages for me.

If that doesn't work for you, you can try submitting a query to: gcp(at)globecargova.org
Greg Goodavish

Post by Greg Goodavish »

Yes, I did that. Still does it.
Greg Goodavish

Post by Greg Goodavish »

Is anyone able to correct the date on my pirep in my logbook? If not, no biggie, as long as you realize my November flight is showing up as being flown in August 1, 2005.
User avatar
esurfman
Member with over 30 posts
Posts: 1808
Joined: Mon Jul 05, 2004 6:38 pm
Location: Montreal, Quebec Canada

Post by esurfman »

Change done. Next time you can send and e-mail to me your admin (nsa.....) will do it free of charge. :wink:
Louis Sanson
Pilot 1068
Captain 747-400 777-200/300 737
Image
Vatsim id # 964473
Greg Goodavish

Post by Greg Goodavish »

Thanks, Louis. Hopefully, there won't be a next time, right? :oops:
Post Reply