757-200PF performance data

[kberry]

I recently started experimenting with cargo and picked up a small fleet of 757-200PFs. After looking at the range/payload numbers on AWS I notice they seemed a bit off compared to what I know of RW airline users (namely UPS, FedEx and DHL) operations. For instance I know FedEx used to do MEM-ANC somewhat regularly with their 752's (3100nm or so) which is not possible here without a significant weight penalty. I went looking on Google and came up with a PDF made by Boeing with more accurate numbers. Pages 13-14 contain the tables showing range at 2935nm for RB211-535E4-B equipped aircraft or 3150nm for PW2040 equipped aircraft. Even the weaker engine options not simulated here (PW2037 and RB211-535E4) have longer ranges than the 2470/2490nm on AWS. There's also payload-range charts in the same PDF. I'd propose adjusting the range to match Boeing's numbers.

(source: http://www.boeing.com/resources/boeingdotcom/company/about_bca/startup/pdf/freighters/757f.pdf)

[Talentz]

Hello.


From your own Doc, the max payload range is around 2500nm for the <115 660 kg/PW2040> MTOW variant. In AWS, the range is 2470 for Max payload. Not Volume-limited payload. Two different numbers to base your numbers on. Also, at 3100nm with the PW2040 engines, the payload is 32,583kg. Considering the max payload for the aircraft is 38,260kg, not sure where the "significant weight penalty" is coming from.

Also, just so were on the same pdf, that Doc is one of the data sources used to compute the 757PFs data, among others.


Talentz

[kberry]

From your own Doc, the max payload range is around 2500nm for the <115 660 kg/PW2040> MTOW variant.

I went back and checked (twice) and couldn't find that 2500nm number anywhere in the doc in question.

Also, at 3100nm with the PW2040 engines, the payload is 32,583kg. Considering the max payload for the aircraft is 38,260kg, not sure where the "significant weight penalty" is coming from.

The difference between 38260kg and 32583kg (5677kg) is a hair over 15%. I'd call that pretty significant.

I DID however have a look at the MEM-ANC trip example and it shows as 2733nm in the AWS system (the 3150 I referenced in my original post was statute miles instead of nautical miles) which IS possible with a full load in AWS so I was definitely mistaken there. Serves me right for using FlightAware as a source and not looking hard enough.

[MikeS]

I went back and checked (twice) and couldn't find that 2500nm number anywhere in the doc in question.

You can read it off the chart on pdf page 15