Flight Plan/Check Airspaces should take into account flight plan's altitude

[MGiacomet]

The "Check Airspaces" feature currently disregards airspaces' altitude limits when creating the list of airspaces in the route of flight.

I realize not all airspaces (e.g., TFRs) have clear cut, well described, altitude limits but where able or where the flight path crosses well defined airspaces (e.g., Class B, C, D) if should not list those airspaces if the desired flight plan altitude does not penetrate them. Listing ALL airspaces regardless of altitude, diminishes the utility of the feature, as a person can simply look at the chart and see where the flight path passes thru.

 

[John Bowen]

I prefer that all airspace’s are depicted. Say you are flying along and decide to descend to avoid weather, turbulence, etc. If the Class B, C, etc. airspace is not depicted, you may inadvertently pass into it without knowing.

 

[MGiacomet]

I prefer that all airspace’s are depicted. Say you are flying along and decide to descend to avoid weather, turbulence, etc. If the Class B, C, etc. airspace is not depicted, you may inadvertently pass into it without knowing.

Perhaps my explanation of the feature request wasn't clear...

My request is for the PLANNING phase of the flight to only warn about airspaces for which the PLANNED altitude (and route) will penetrate. If one PLANS a flight, say for 7000ft, only airspaces for which that PLANNED altitude of 7000ft (and route) should be in the list.

Now, if you are flying along and decide to descend, if you rePLAN your flight because of that, you'll be warned of those airspaces that the newly PLANNED altitude will penetrate. But... if you do NOT rePLAN, then the normal airspace warnings will still pop up as you are flying along.

If one wants know ALL the airspaces the flight could penetrate regardless of altitude, one can always look at the sectional...

See pictures below, for an example.
Planning a flight KFPR-KPBI


Planned cruise altitude of 6500ft (flight does not penetrate KSUA airspace)




Yet a warning is issued for it... Shouldn't.

 

[John Bowen]

OK, I see what you mean now…