RNAV

Items per page   10 | 25 | 50 | 100
11 to 20 of 26 results

Stakeholder panel urged for RNAV route development

Advocacy | Jan 22, 2014

AOPA is urging the FAA to improve its development of RNAV terminal routes (T-routes) as ground-based navaids are decommissioned.

Mentor Matters: Missing glideslope in San Juan

Pilot Magazine | Dec 01, 2013

With the release of its WAAS-equipped flight decks and stand-alone navigation units, Garmin introduced advisory vertical navigation capability for nearly all RNAV approaches, not just those that have published WAAS minimums.

Flight plan changes take effect

Article | Oct 24, 2013

Effective Oct. 24, the FAA has replaced some of the suffixes used to describe on-board equipment in domestic flight plans.

ICAO flight plan now required for all border crossings

Article | May 15, 2013

Mandatory use of International Civil Aviation Organization flight plans has expanded to include all border crossings, even if only an overflight.

New ATC phraseology for RNAV approaches

Article | Apr 30, 2013

Instrument pilots flying RNAV-equipped aircraft should expect to hear some slightly different phraseology from air traffic controllers beginning June 3.

FAA eases IFR departure rule for RNAV aircraft

Advocacy | Feb 25, 2013

The FAA, making an exception to a standing rule, has begun to permit aircraft using satellite navigation to receive clearances and depart under IFR from nontowered airports more than 40 nautical miles from an operating ground-based navigation aid, and without radar monitoring.

IFR Fix: Crossing LAFLN

IFR Fix | Feb 08, 2013

Checking the chart to see what lies ahead along the airway, you scrutinize an intersection 14 miles distant, where another airway crosses. There's a difference in the low-altitude enroute chart's depiction of how each airway arrives at the fix.

FAA proposes RNAV route modification in Alaska

Advocacy | Jan 24, 2013

The FAA has proposed to modify low-altitude RNAV route T–266 in Alaska by removing two nondirectional beacons (NDBs) from the route description and replacing them with RNAV waypoints. Members are encouraged to submit comments on the proposal by March 8.