Jump to content

Will C

members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Will C

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

496 profile views
  1. I've seen some FAA-style routes on dispatch paperwork from USA domestic regional carriers... but they're from several years ago. As for making a PFPX OFP with an FAA style route -- It's probably not worth the trouble, but thanks for the offer.
  2. Similar to the issue of TOPCAT importing only values in hectopascals (and not inHg) into PFPX flight plans, it looks like the ATC ROUTE is permanently stuck in ICAO format as well? I can change "Output" to "FAA" in preferences, and then within the PFPX route window, the flight plan shows up in FAA format, but when it comes to the OFP, the version reverts back to ICAO. Not a big deal, I suppose.
  3. Thank you, that's very helpful. Regarding the boldface parts of the ATC ROUTE, are they supposed to be intelligible to the flight crew? Here's the first one again: N0501F350 Given what you said about changes in speed and/or altitude, I'll deduce that the F350 indicates an initial climb to FL350. That indeed fits with the flight plan. And the subsequent xxxxxF370, xxxxxF370, and xxxxxF410 all make sense now. (Except that I would have expected an intermediate segment at FL390, but that's a question for another day perhaps.) But what about the first five characters (N0501)? Some kind of code? Again, is the flight crew intended to understand it? Thanks for your time.
  4. Hello, I can't find this information elsewhere, so I thought the forum might be able to help. I can understand everything on the attached OFP except for the sections highlighted in blue. 1. MFT - What does this stand for? 2. AIR DIST - How is this different than the F/P DIST? 3. ETD, ETA, PLN - How are these different than STD, STA, SKD? It looks like the second set might be based on a generic no-wind scenario, with ETD, ETA, PLN being the times modified for current weather... is this correct? 4. COMP and HD011 - What are these? 5. MSA - Minimum sector altitude, or something else? 6. LEG, ACC, ETO / ATO - What do these mean? And then one other question, not related to anything in blue text... under ATC ROUTE, the route is this: N0501F350 N0501F350 SNTNA2 SYRAH Q128 FLOOD J28 PUB J64 HLC DCT IRK DCT RBS/N0501F370 DCT FWA DCT DJB/N0503F410 DCT SLT DCT LVZ LENDY6 (Boldface added.) Meanwhile, the route within PFPX looks like this: SNTNA2 SYRAH Q128 FLOOD J28 PUB J64 HLC DCT IRK DCT RBS DCT FWA DCT DJB DCT SLT DCT LVZ LENDY6 The second version is much more familiar to me. What are we to make of the information in boldface in the OFP? They look like waypoints but I can't understand why there would be needed in the OFP. Thanks for your help, everyone. OFP.pdf
  5. Problem solved - I moved the decimal point a bit when inputting the fuel flow, and the resulting fuel bias was out of limits. Getting the decimal point right solved the problem.
  6. So, I opened up the Aircraft Performance Monitor (APM) to enter a new reading. I typed in the requested values from my sim (gross weight, flight level, cost index, TAT, TAS, ground speed, etc.) and eventually every box was filled. I put in the requested data, and PFPX calculated the remainder. Like I said, every field had a value in it, and nothing appeared to be in error (nothing was red, etc.). But the "Add" button at the top of the window was greyed out. Only the "Cancel" button worked. Are there any tricks to being able to add a new value? Thanks!
  7. I guess it can't be changed. At least it's good to know for sure. Thanks again!
  8. Hi, I posted on this before but now I have more information. The issue is that PFPX calls TOPCAT for the takeoff and landing data, and then brings the altimeter setting back in hectopascals, which gets passed to the OFP, even when the airport is located in a region in which inches of mercury would be preferred. Attached is a screenshot of PFPX calling TOPCAT for takeoff information from Chicago O'Hare. You can see that PFPX/TOPCAT is fetching the altimeter setting in inches of mercury, and interpreting the METAR correctly - you'll see that under "Pressure," the correct numbers 30.06 are displayed. However, when you look at the results window (this is the information that TOPCAT will append to the OFP), you'll see that the altimeter setting is in hectopascals ("QNH 1018"). You'll see it in the line that reads: TEMP +2C QNH 1018 WIND 130/12 (09KT HW) (emphasis added) That line is brought into the PFPX flight plan verbatim. I'm guessing that TOPCAT is looking at a config setting somewhere that requests results be given in hPa, but for the life of me I can't see where that would be. The PFPX file for the aircraft I'm using has the units set at feet and pounds. Under TOPCAT performance module, the file that is called is Boeing 747-400 RB211-524H, but I'm not sure what that links to or even if it's the problem. Within TOPCAT, I have only one aircraft in the aircraft database, and under "Aircraft Details," the pressure units are listed as inches of mercury. Inside the TOPCAT "Aircraft" folder, the files are unreadable to me (i.e., not readable by a standard text editor). Inside the TOPCAT "Configurations" folder, I can see some readable configurations but I can't see a line for setting a preference for the altimeter setting. That's all I can think of. Can anyone help me get TOPCAT to send inHg to PFPX? Thanks!
  9. I used PFPX to plan a flight within the continental United States, where METARs give the altimeter settings in inches of mercury (inHg). When the OFP was generated, however, the field conditions at both the origin and destination airports are given on the OFP in hectopascals (hPa). I can't find a setting in PFPX to change the OFP units from hPa to inHg. Does this exist? If so, where? Thanks!
×
×
  • Create New...