Sender: <marv@lancaironline.net>
To:  lml@lancaironline.net
Date: Wed, 18 Apr 2012 11:00:39 -0400
Message-ID: <redirect-5487047@logan.com>
Received-SPF: none
 receiver=logan.com; client-ip=98.138.91.179; envelope-from=casey.gary@yahoo.com
DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=3p11dKu5q+B7YY+HANeELGMQfSoxqVb/Vq/3jknfq54DoErJSrmZ+6U5mZ4/sGSRTGHEa93wvXy04ybWjYN7xwuTSiB1xXvJKOi+3Y8U1OyFV2tro1NZpvSnjQ/VwbYYZVspEMg/60ue+zhaJiRgKHJ/d3QYnHzaCon2a5eJe08=;
References: <listdigest-5486395@logan.com>
From: Gary Casey <casey.gary@yahoo.com>
Reply-To: Gary Casey <casey.gary@yahoo.com>
Subject: Re: ensure your transponder works
In-Reply-To: <listdigest-5486395@logan.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-685807438-1779662783-1334749150=:11274"

---685807438-1779662783-1334749150=:11274
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Ralf,=0AI'd like a little more detail. =A0I assume you were not talking (ge=
tting flight following services) to ATC all along, right? =A0I don't know t=
he details of the Class B airspace around Newark, but I also assume you wer=
e flying inside the Mode C 30-mile circle, but outside Class B airspace, ri=
ght? =A0That's the only time I can imagine getting a "Mode C violation." =
=A0If you were getting flight following services I can't imagine them not t=
elling you they weren't receiving your Mode C return. =A0And, of course, if=
 only the altitude encoding function were inop the Xponder would still be s=
howing reception (blinking light) and would be transmitting a reply. =A0I a=
nd my neighbors often fly under the Denver Class B without talking to ATC. =
=A0hmm.... =A0So, yes, user beware - you could violate the Mode C airspace =
and never know it - until later. =A0I suppose the only defense would be to =
talk to ATC whenever anywhere near the 30-mile radius.=0A=0AThe other post =
about ATC getting in a snit because of 20 minutes of radio silence - that's=
 surprising as I've had just that occurrence many times over the years, usu=
ally resulting in me looking up the nearest frequency on the chart and reco=
vering communication. =A0But it was usually out in the middle of nowhere, n=
ot in Florida (wait, is that also nowhere? :-). =A0I'm surprised FAA is pus=
hing back so hard.=0A=0AJust two examples of a "kindlier and friendlier" FA=
A, or are we in a new era? =A0I think I know the answer. =A0An anecdote: =
=A0My transponder replies with my registration number, but I didn't know th=
at until I had flown my ES for 3 years or so, including all over LA. =A0Doi=
ng a Xponder cert, the technician asked, "why don't you have the correct N-=
number programmed?" =A0Huh? =A0So I programmed in the right number - I had =
been flying for years with me telling ATC one number and my Xponder telling=
 them another. =A0Nobody complained, so I assume they weren't watching. =A0=
Or?=0A=0AGary Casey=0A=0ADear subscribers=0A=0ALast week I flew from my hom=
e airport in Ohio to the Linden Airport=0A(KLDJ - about 10 miles south of N=
ewark). I flew into this airport IFR=0Abefore and I recall the controller a=
sking me if I could finish my flight=0AVFR because of all the traffic in th=
is area. This time I decided not to=0Abother anybody and go VFR from the st=
art since the weather was fine.=0A=0AI had a Garmin 320 transponder and the=
 amber light was happily flashing=0Aall the way to New York. What I did not=
 know was that the transponder=0Afailed and was not sending out a signal...=
.=0A=0AWhen I landed the airport stuff came up immediately and told me to c=
all=0ANY FAA. They filed then a Mode C violation and told me not to move th=
e=0Aplane without permission.=A0=0A.....=0AAfter explaining the FAA that th=
e old transponder failed and I had a=0Areplacement in place I got permissio=
n to leave Linden the next day. The=0Anew transponder works and everybody c=
an see me again. The FAA indicated=0Athat since I have a work order for tes=
ting the old transponder (Tom=0AMadden's recommendation) they will drop my =
charges.=0A=0ARalf=0A
---685807438-1779662783-1334749150=:11274
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:bo=
okman old style, new york, times, serif;font-size:12pt"><div>Ralf,</div><di=
v>I'd like a little more detail. &nbsp;I assume you were not talking (getti=
ng flight following services) to ATC all along, right? &nbsp;I don't know t=
he details of the Class B airspace around Newark, but I also assume you wer=
e flying inside the Mode C 30-mile circle, but outside Class B airspace, ri=
ght? &nbsp;That's the only time I can imagine getting a "Mode C violation."=
 &nbsp;If you were getting flight following services I can't imagine them n=
ot telling you they weren't receiving your Mode C return. &nbsp;And, of cou=
rse, if only the altitude encoding function were inop the Xponder would sti=
ll be showing reception (blinking light) and would be transmitting a reply.=
 &nbsp;I and my neighbors often fly under the Denver Class B without talkin=
g to ATC. &nbsp;hmm.... &nbsp;So, yes, user beware - you could violate
 the Mode C airspace and never know it - until later. &nbsp;I suppose the o=
nly defense would be to talk to ATC whenever anywhere near the 30-mile radi=
us.</div><div><br></div><div>The other post about ATC getting in a snit bec=
ause of 20 minutes of radio silence - that's surprising as I've had just th=
at occurrence many times over the years, usually resulting in me looking up=
 the nearest frequency on the chart and recovering communication. &nbsp;But=
 it was usually out in the middle of nowhere, not in Florida (wait, is that=
 also nowhere? :-). &nbsp;I'm surprised FAA is pushing back so hard.</div><=
div><br></div><div>Just two examples of a "kindlier and friendlier" FAA, or=
 are we in a new era? &nbsp;I think I know the answer. &nbsp;An anecdote: &=
nbsp;My transponder replies with my registration number, but I didn't know =
that until I had flown my ES for 3 years or so, including all over LA. &nbs=
p;Doing a Xponder cert, the technician asked, "why don't you have
 the correct N-number programmed?" &nbsp;Huh? &nbsp;So I programmed in the =
right number - I had been flying for years with me telling ATC one number a=
nd my Xponder telling them another. &nbsp;Nobody complained, so I assume th=
ey weren't watching. &nbsp;Or?</div><div><br></div><div>Gary Casey</div><di=
v><br></div><div><span class=3D"Apple-style-span" style=3D"color: rgb(69, 6=
9, 69); font-family: arial, helvetica, sans-serif; font-size: 13px; ">Dear =
subscribers<br><br>Last week I flew from my home airport in Ohio to the Lin=
den Airport<br>(KLDJ - about 10 miles south of Newark). I flew into this ai=
rport IFR<br>before and I recall the controller asking me if I could finish=
 my flight<br>VFR because of all the traffic in this area. This time I deci=
ded not to<br>bother anybody and go VFR from the start since the weather wa=
s fine.<br><br>I had a Garmin 320 transponder and the amber light was happi=
ly flashing<br>all the way to New York. What I did not know was that the
 transponder<br>failed and was not sending out a signal....<br><br>When I l=
anded the airport stuff came up immediately and told me to call<br>NY FAA. =
They filed then a Mode C violation and told me not to move the<br>plane wit=
hout permission.&nbsp;<br>.....<br>After explaining the FAA that the old tr=
ansponder failed and I had a<br>replacement in place I got permission to le=
ave Linden the next day. The<br>new transponder works and everybody can see=
 me again. The FAA indicated<br>that since I have a work order for testing =
the old transponder (Tom<br>Madden's recommendation) they will drop my char=
ges.<br><br>Ralf<br></span></div>  </div></body></html>
---685807438-1779662783-1334749150=:11274--