PEAware Is Killing My Soul.....

[Nelson L.]

http://peaware.pilotedge.net/flight.cfm?id=107062

TPX783 KLAS-KSAN. After a normal 45 or so minute flight to Lindberg I shoot the LOC 27 and go missed due to not being able to break out of the clouds. Try again a second time and same result, a go-around.... I proceed to enter the published hold on the missed at Sargs for about 20 or so minutes, then divert to Gillespie due to minimum fuel (which Joe did some sort of dark-magic math to figure out..... newfound respect for the airline pilots who have to do the math every preflight). Visual 27R at Gillespie, go-around because of way too high approach (*sigh*... I know), go back in left traffic and land safely. Left the gate at Vegas at 20:05 Pacific and got the gate at Gillespie at 21:51 (which I know because I had to log it for my Excel logbook). In the meantime, I go to PEAware to blissfully look at the 120 or so minutes added on to my flight time (I'm a PEAware fanatic), but it showed that I had an 18 minute flight!?? Apparently it started calculating when Marcus (the controller on at the time) changed my destination to Gillespie (as he should have done to make PEAware log the flight), PEAware restarted itself..... Aghh! Hopefully this will be fixed eventually, my heart has been broken!

(don't call me dramatic, I live for PEAware )

http://assets.pilotedge.net/recordings/ ... _17510.mp3 - 6:30 My proudest moment!!!

Edit - (I did forget to read back 5000, although I did climb to 5000.... I just didn't read it back)

[rtataryn]

Similar experience happened to me a few weeks ago.

http://peaware.pilotedge.net/flight.cfm?id=102624

I was on a night IFR flight from KTOA to KRNM and the airport went below minimums for the VOR approach, so I asked for a clearance and vectors for the ILS to Palomar which was just a super quick turn to the north to join it. So fast in fact that I barely had time to pull up the chart, tune the localizer frequency and dial in the approach course before the needle started to come in. Anyway, when I reviewed my flight on PE Aware I found that it had only logged me for 8 minutes, the time to shoot the missed at Ramona and land at Palomar. Come to think of it Marcus was on that night too . . . But man that guy was busy.

[Nelson L.]

Don't blame Marcus - pure coincidence. Joe explained that apparently when someone diverts, part of the controller's requirements are to change the flight strip with the amended destination (since PEAware can only log the flight if you land at the "destination" airport). But then again, I don't know why I'm sparing Marcus when he insists on giving us the FASTO1 arrival into Bakersfield in lieu of the company route (joking)!

PS - Technically, you can't file 0 knots for speed

[rtataryn]

Oh, I know it isn't the controller. (hence the smiley) PE Aware does it every time I go missed and divert. It happened on my I-10 and logged me for only 23 minutes - just for the leg from the hold at GLJ to KSBP. No big deal, but I agree it would be nice to see a fix and have an accurate time log. But the 0 knots for airspeed??? Definitely gonna pin that on Marcus.