Calibrated airspeed

[beno]

Recently I found out, that at higher speed (over 100kt) I get approx. 10kt difference between IAS and CAS (IAS and TAS is to high), at 70kt it is fine. The source of error is likely pitot location, which cannot be changed. Based on wrong TAS I get also wrong wind calculation.

I cannot find any possibility in Skyview to define airspeed corrections. I think, making software feature for CAS calculation would not be complicated.

 

[dynonsupport]

There isn't a way to adjust IAS in SkyView right now. It's not something we have received much demand for, and in most airplanes the issue is static location, which requires some complex tables to correct for static pressure over airspeed.

 

[beno]

I think, people probably do not ask for that because, many times they are not aware.

Such a table could be prepared on computer and uploaded as a file to Skyview. Would be a very nice feature, because changing pitot position is practicaly impossible. Without that correction, wind information is not unusable.

 

[GalinHdz]

There isn't a way to adjust IAS in SkyView right now. It's not something we have received much demand for, and in most airplanes the issue is static location, which requires some complex tables to correct for static pressure over airspeed.

What about a IAS to CAS correction factor that the user can enter airplane specific data? The default can be 0 across the entire range.

Example:
IAS        CAS
40Kt     +12Kt
60Kt     +10Kt
70Kt     +6Kt
80Kt     +3Kt
90Kt       0Kt
100Kt    -2Kt
110Kt    -2Kt
120Kt    -4Kt
130Kt    -7Kt
140Kt    -10Kt
And so on.

I have a IAS to CAS graph that is very accurate. The Skyview would use the CAS numbers for its calculations. Maybe even have the option of displaying either the IAS or CAS on the airspeed tape. 

 

[dynonsupport]

Again, there isn't a way to adjust IAS in SkyView right now, nor is such a feature planned for the immediate future.

 

[bbtapb]

Unless your pitot tube is behind the prop or too close to a compressing surface, it's likely static error. Try putting a 4x thick piece of masking tape in front of your static port.

Better to fix your static port than try to deal with it in software.