Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
It may be the case, but the division is the correct way to do it. 0.6 comes from the FARs that state 60%. 60% is 60 out of 100 or 6/10 or 0.6. Multiplying by 1.67 is not quite the same, and yields a slightly higher number than dividing by 0.6
This is one of the most misunderstood aspects in 135 flying. Everyone thinks you factor the landing distance given in your AFM. Actually you factor the runway.
Example:5000ft rwy X .60=3000ft required. If your AFM landing distance is 3000 or less you meet the 60% rule. Most people look at the landing distance and multiply it by 1.6. end quote}
In this example, 8900.1 gives an example on how to factor in th 60%.
4)Runway conditions (including contamination). Runway features, such as slope and surface composition, can cause the actual landing distance to be longer than the calculated landing distance. Wet or slippery runways may preclude reductions from being taken and, in fact, require 115 percent of the distance derived from calculations, whether a reduction was used or not. This distance is calculated by increasing the distance required under dry conditions by an additional 15 percent (i.e., if Aircraft Flight Manual (AFM) data shows the actual landing distance will be 2,000 feet, the effective runway length required is 3,334 feet using 60 percent in this example. If the runway is expected to be wet or slippery upon arrival, the effective runway length required is 3,834 feet). Braking action always impacts the landing distance required as it deteriorates. Always consider the most current braking action report and the likelihood of an update prior to the flight’s arrival at a particular airport.
In their example, they factor the AFM numbers and not the runway. This is the way I have been doing this for years.
By using this example, you would not divide the runway legnth by .6, but the AFM numbers.
Who is correct?
Starcheckdriver is correct..