The KR1 and KR2 have pre-filled performance data templates, at least as far as in the Centers goes. So, when calling for flight following, you can identify as either "experimental KR1/KR2" or straight "experimental." If the controller asks for specific type, you can respond with the KR1/KR2 and the system will accept it. The system will use template speeds (130 KTAS for the KR1 and KR2) and climb/descent rates (1000 FPM for KR1 and KR2) for conflict alert processing. If these vary significantly (+/- 5% or 10 kts, whichever is greater), advise ATC of your actual value. The system does not discriminate between a KR2 and KR-2S, so the type call for both has to be "KR2." None of that is required, of course, as "experimental" will suffice, as Mr. Flesner pointed out. But it helps the controller out when issuing traffic calls to know the type of aircraft involved. Or, in cases like me, satisfies pure curiosity :) Also, as I'm sure most of you know, VFR flight plan information does not transfer to ATC facilities; it is strictly a function of Flight Service. So, if you do file a VFR plan (as I hope you all do anyway), understand that the controllers will not know what you do (be nice!), such as what your filed TAS and route is. For example, if you're flying from Aberdeen SD to Rapid City SD, the controller will enter it as a direct flight, even though you may have filed on the VFR plan to go over Pierre instead of direct. In a case like that, I'd suggest that after getting radar identified, tell the controller what your route plan is if it's anything besides direct.
Thanks for listening and safe flying! -Matt Reed KR-2S, 75% Long EZ, 10% I just need one more project, then I can say I have 100% of an airplane... > Date: Thu, 26 Jun 2014 16:12:37 -0500 > To: krnet at list.krnet.org > Subject: KR> Radio call type designator > From: krnet at list.krnet.org > > At 08:50 AM 6/26/2014, you wrote: > >Maybe a silly question but what do you use as a type designator when > >calling ATC in your KR2? Experimental? KR? > >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > from the Airman's information > manual: https://www.faa.gov/air_traffic/publications/atpubs/aim/aim0402.html > > 3. Civil aircraft pilots should state the aircraft type, model or > manufacturer's name, followed by the digits/letters of the > registration number. When the aircraft manufacturer's name or model > is stated, the prefix "N" is dropped; e.g., Aztec Two Four Six Four Alpha. > > EXAMPLE- > 1. Bonanza Six Five Five Golf. > > 2. Breezy Six One Three Romeo Experimental (omit "Experimental" after > initial contact). > > > Personally, I start the call with "experimental" rather than end with same: > > Example: Marion tower - experimental KR- 211LF- > > Any additional communications simply ends with - 1LF > > Granted,, not one in 50 controllers will know what a KR is but I gave > them the required information. If they have questions, they can > ask. At my home field where they know "what or who" I am, I often > omit the "KR" in the initial call. Example " Marion ground - > Experimental 211LF". After their reply it's "1LF - Midwest hangar - > taxi - VFR - northwest departure". Short and sweet and they have all > the info they need. If I want a runway other than what I know they > will assign, I include that request in the second > contact. Example: " "1LF - Midwest hangar - taxi - VFR - request > runway 2 at Bravo for a northwest departure". > > Know what you're going to say before you key the mike. Just tell > them who you are, where you are, and what you want or what your > intentions are. Keep it simple. > > Larry Flesner > _______________________________________________ > Search the KRnet Archives at http://tugantek.com/archmailv2-kr/search. > To UNsubscribe from KRnet, send a message to KRnet-leave at list.krnet.org > please see other KRnet info at http://www.krnet.org/info.html > see http://list.krnet.org/mailman/listinfo/krnet_list.krnet.org to change > options
