<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Takeoff and landing airpot elevation exceeds 8000 ft]]></title><description><![CDATA[<p dir="auto">How do I operate the aircraft at airports with takeoff and landing elevations above 8,000 feet? For example, Bogotá (SKSO) at 8,350 feet.</p>
]]></description><link>https://community.justflight.com/topic/10837/takeoff-and-landing-airpot-elevation-exceeds-8000-ft</link><generator>RSS for Node</generator><lastBuildDate>Thu, 02 Jul 2026 04:27:58 GMT</lastBuildDate><atom:link href="https://community.justflight.com/topic/10837.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 30 Jun 2026 18:38:58 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Takeoff and landing airpot elevation exceeds 8000 ft on Wed, 01 Jul 2026 10:22:04 GMT]]></title><description><![CDATA[<p dir="auto">The takeoff/landing performance data that we have access to for the F70/F100 is from an airline that didn't operate at high-altitude airfields, so the performance data only covers airfield elevations from 0ft to 8,000ft. This, I believe, was the standard takeoff/landing performance data that all airlines received, regardless of the airfield altitudes they were operating at.</p>
<p dir="auto">We did recently receive some performance data for an airline that used to operate at high-altitude airfields, and it appears that they had specific performance data for every high-altitude airport they operated at. I.e. there isn't a single graph that covers all airfield elevations from 0ft to 12,000ft, they instead used the 0ft to 8,000ft graph to calculate performance in that range, and then had flap 0 (dry), flaps 0 (wet), etc. performance tables for every airport they operated at above 8,000ft.</p>
<p dir="auto">With the performance data being airport-specific (based on runway length, slope, elevation, surrounding terrain, etc), that makes it tricky to implement the data into the performance calculator without extensively extrapolating the data (which would come at the cost of accuracy).</p>
<p dir="auto">We do plan on looking into this further once we implement the more powerful Tay 650 engines, which have different performance data.</p>
<p dir="auto">Mark - Just Flight</p>
]]></description><link>https://community.justflight.com/post/51712</link><guid isPermaLink="true">https://community.justflight.com/post/51712</guid><dc:creator><![CDATA[Mark]]></dc:creator><pubDate>Wed, 01 Jul 2026 10:22:04 GMT</pubDate></item></channel></rss>