I flew a Delta 777-200L from OMDB to KMSP yesterday. PFPX slotted me into North American airspace via the northernmost westbound NATRACK. With 100+ Kt tailwinds my ground speed was 580 Kts in LRC.

 

I use PFPX, ASN and EFB to plan and follow the flight progress. EFB tracks time over waypoints, ETE, and fuel burn which aids greatly in making enroute decisions. The PFPX numbers on fuel load and burn have always been conservative with long haul fuel on board at destination running around 30,000 to 40,000 lbs, depending on alternates, etc. I was quite surprised that the forecast held true given the tailwind experienced on this flight. I follow the FMC flight plan with steps at LRC which compares to my PFPX entries.

 

BTW Dan,we always program our computations in english units and convert them to metric in the User Interface to prevent mixing english and metric units in our computational modules. It's an easy mistake to make programming wise and it's my guess that's what PFPX will find in your bug. We usually trap unexpected or out of range computational error in our I/O modules but if one such as dividing by zero gets missed, the hardware AU kicks out an interrupt that stalls the processing resulting in a freeze.

May I ask if cargo capacity needs to be filled out?