REFLECTOR:Nav Requirements

reflector@tvbf.org reflector@tvbf.org
Fri, 16 Jan 2004 11:01:57 EST


--part1_137.29f9f1f3.2d3964f5_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Joe:
FAR 91.205(d) spells out the legal requirements for instruments for IFR 
flight.  Legally, all you need is a "navigational instrument for the ground 
facility to be used."  So, technically if all you are going to do is fly VOR airways 
and shoot a VOR non-precision approach, all you need is one VOR, period.  Of 
course, this is not the wisest way to fly IFR, and I would not recommend it.  
In your case if you have an IFR certified GPS/moving map that you are 
comfortable with to use for GPS approaches and as a supplement for VOR and ILS 
approaches, a VOR with VOR/ILS capability is legal and should be adequate.  All you 
would be missing is ADF, but unless you are using a field that has that an NDB 
approach, you can do without it.
Manny Lewis, CFII

--part1_137.29f9f1f3.2d3964f5_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><HTML><FONT  SIZE=3D2 PTSIZE=3D10 FAMILY=
=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0">Joe:<BR>
FAR 91.205(d) spells out the legal requirements for instruments for IFR flig=
ht.&nbsp; Legally, all you need is a "navigational instrument for the ground=
 facility to be used."&nbsp; So, technically if all you are going to do is f=
ly VOR airways and shoot a VOR non-precision approach, all you need is one V=
OR, period.&nbsp; Of course, this is not the wisest way to fly IFR, and I wo=
uld not recommend it.&nbsp; In your case if you have an IFR certified GPS/mo=
ving map that you are comfortable with to use for GPS approaches and as a su=
pplement for VOR and ILS approaches, a VOR with VOR/ILS capability is legal=20=
and should be adequate.&nbsp; All you would be missing is ADF, but unless yo=
u are using a field that has that an NDB approach, you can do without it.<BR=
>
Manny Lewis, CFII<BR>
</FONT></HTML>
--part1_137.29f9f1f3.2d3964f5_boundary--