|
|
Micah,
I answered this for you on the EFIS forum today, but here it is for
others. I got it straight from chelton.
-----
Here's what you can do about Private Airports and Terrain Warnings (per Chelton):
First, check the version of TAWS configured in the system. Anything greater than Class-C is a waste and will cause the system to generate nuisance callouts all of the time. You may be programmed for Class-A.
Second, designate the user waypoint as a "runway" by selecting a bearing on the waypoint. This is done by going into the "Edit User Waypoints" section of the flight plan and setting the bearing to whatever the bearing of the runway is. Then, when you're ready to fly to the airport, you needs to select "VFR Approach" to the user waypoint. (Using the ACTV button and associated steps)
Last, if you have an IDU-III system, you should have a TAWS INHIBIT switch that you can activate. If it is an IDU-I system, then selecting the VFR approach to the waypoint should eliminate the majority of the callouts.
I hope that helps!
Tim
Micah Froese wrote:
Looking for a solution to an annoying problem. I am based at SC99, a private airpark. Each time I take-off or land, my Chelton fires off a barage of warnings. (terrain, obstruction) Warnings start in the pattern, and don't end until shutdown. SC99 is entered in as a waypoint. What are some of the possible solutions to this issue?
Thanks,
Micah Froese
Lancair Legacy
182 hours
-- For archives and unsub http://mail.lancaironline.net:81/lists/lml/List.html
|
|