|

Flying the Hudson River Corridor

Ever since I moved out to the Philadelphia area, the Hudson River corridor in New York City has become one my favorite places to fly. It’s hard to overstate the beauty of the city from low over the river. Every time I have a family member or friend come to visit, I try and take them over to see the city from the air.

Each time I fly up the river I can’t believe that we are actually allowed to do so, flying below the tops of the buildings and close enough that you feel that you could reach and out touch them. The draw back to the Hudson River Corridor is that it can be busy, intimidating, and confusing. However, with some reading and preparation, the Skyline flight is easy to do and extremely rewarding.

Having the right weather is an important first step. The second step is try to arrive during ideal lighting conditions. If possible, select a smooth, calm day to make it easier to maintain a track down the correct side of the river. I always try and target arrival at the city around sunset. The view is spectacular any time of day, but having the lights from the city while the sun is just setting gives the best viewing. I’ve also flown over and done the whole flight after dark, which is always spectacular.

View of the World Trade Center

The first method of flying the river is to utilize VFR flight following. If the controllers aren’t too busy, they will provide advisories to aircraft that request the Skyline. The nice thing about doing it this way is that the controller will clear you into the NY bravo airspace and keep you above the traffic flying the Skyline in the VFR corridor below. This is the method that I have always preferred as I enjoy the added benefit of the traffic advisories and it’s nice not to worry about position reporting on the radio.

If you want to get flight following, head toward the corridor and request the Skyline route with NY Approach. (Remember to stay clear of the Bravo until you’re cleared in!) Once you’re cleared into the Bravo and approaching the corridor, they will hand you off to Newark/ LaGuardia Tower for traffic advisories over the river. I like to approach from the south and ask for a 180 over the George Washington Bridge. This allows me to fly past the city a second time before exiting the corridor over the VZ (Verrazano Bridge) and heading back toward home.

In red is the path I typically fly. I descend to 1400’ and fly toward the APPLE intersection picking up the shoreline around Staten Island and hugging it until crossing the middle of the VZ. Newark normally clears me into the Bravo at 1400’ or 1500’ to fly up the corridor.

Pros:

  • Better traffic Awareness
  • No position reports

Cons:

  • Flying slightly higher reduces the view
  • If the controllers are busy, they may deny your request for advisories  
  • Can be intimidating to talk to NY Approach/ Newark/ LaGuardia 

The other option is to fly in the VFR corridor. If you want to do it via this method there are just a few things you need to make sure you’re familiar with before you go. When in the VFR corridor you’ll need to make required position reports on a CTAF frequency. Make sure that you have the proper charts and have studied pictures of the landmarks so that you know what you’re looking for. I tend to plan on this as a backup in the event that the controllers won’t give me advisories.

Pros:

  • Doesn’t require talking to controllers/ class B clearance
  • More freedom to select altitude and routing as desired

Cons: 

  • Less traffic awareness
  • Required position reporting

All the requirements and guidelines for flying the corridor can be found on the back of the NYC TAC chart. Any pilot flying the river is required to have one of these or a NYC helicopter route chart on board. If you’re using Foreflight, look in the Documents section under FAA Fly Charts and select the NYC TAC chart in order to read the back of page.

Below you’ll find examples of the diagrams/ instructions printed on the back of the NYC TAC charts.

You can see the traffic flow requires northbound airplanes to hug the east side of the river, while the southbound traffic stays on the west side. The VFR reporting positions (listed from North to South) are: Alpine Tower, George Washington Bridge, Intrepid aircraft carrier, Goldman Sachs (clock), Statue of Liberty, VZ (Verrazano Bridge). Each position report should include aircraft type, position, direction, and altitude.

Other things to be aware of:
NYC is always a hotspot for TFR’s. There are often TFR’s for baseball games or presidential movements so make sure to check before you head that way. Additionally, there is a speed restriction in place of 140 kts, though I’m not sure why anyone sightseeing would want to go that fast anyhow.

I realize that all of the procedures and restrictions can be overwhelming, but with the proper preparation, the Hudson Skyline is one of the most incredible places in the world to operate an airplane. There are a lot of things that are easy to get excited about that don’t live up to expectation, but this isn’t one of them. I’ve never taken anyone to the river that wasn’t impressed by what they saw and that’s why I plan to keep going back.

About to cross the VZ looking north toward the city

Similar Posts

  • AOPA Air Safety Foundation Survival Seminar

    The AOPA’s Air Safety Foundation will be returning to Texas this coming week with their After the Crash:  Surviving An Aircraft Accident seminar.  Though aircraft accidents are rare to most pilots, they still happen.  It is best to be prepared with the proper knowledge and supplies in case you are stranded in a remote area while awaiting help to arrive.

    The seminar will cover the following items:

    • How and what to pack in a survival kit
    • Ways to help search parties find you
    • What to do first immediately after the off airport landing
    • How to survive will awaiting rescue

    The seminar will be put on in Houston, San Antonio, and Austin on three consecutive nights, the 20th-22nd, so everyone will get a chance to attend.  The location and times are below.

    No signup is necessary, just show up and be ready to learn.  The seminar does count for WINGs credit and there will be a sign in sheet at each event.

    The AOPA Air Safety Foundation puts on numerous seminars throughout the country during the year covering a wide variety of topics relevant to general aviation pilots.  The content is always interesting and the presenter always knowledgeable and entertaining.  Hope to see you there!

    Tuesday, January 20th

    Wyndham Hotel, Houston West
    14703 Park Row Blvd.
    Houston, TX 77079
    7:00pm-9:00pm

    Wednesday, January 21st

    Doubletree Hotel, San Antonio Airport
    37 NE Loop 410
    San Antonio, TX 78216
    7:00pm-9:00pm

    Thursday, January 22nd

    Omni Hotel, Southpark
    4140 Governor’s Row
    Austin, TX 78744
    7:00pm-9:00pm

    For more information on the event and the locations, please click here.

  • Cirrus SR22 Owner Completes First Solo

     

    Monte and N565TV

    Congratulations to Monte James who, on July 31, 2014, completed his first solo flight!  Monte is the owner of N565TV, a 2007 Turbonormalized Cirrus SR22.  N565TV is a G3 model with an Avidyne panel.  Monte was very excited to complete his solo flight.  He reported very good landings during the flight (he even said the last landing, which was probably his best yet, caused him to break into laughter!).  Texas Top Aviation’s Hank Gibson, Monte’s instructor, took pictures and continued the tradition of cutting Monte’s shirt tail to commemorate the flight.

    Congratulations to Monte!

     

  • Cirrus CAPS Pull in Arkansas

    Cirrus CAPS pull #55 took place at the beginning of November over Fayatteville, AR.  From initial reports, it appears a clamp broke on the oil cooler, causing a loss of oil pressure.  It does not appear that the engine immediately quit, but an annunciator alerted the pilot that the engine was losing oil pressure.  At this point, it appears the pilot elected to do an emergency descent to an airport below him, but ended up not timing it right, missing the airport and pulling the parachute.

    As an experienced Cirrus flight instructor, there appears to be some suspect decision making in handling this operation.  I teach in a Cirrus that if an oil light comes on, given that a pilot has some altitude to work with, it is a better option to physically shut the engine down, leaving control of the situation in the pilot’s hands.  This way, the pilot knows when the engine is stopping and is prepared for it, instead of the engine acting erratically and causing problems on the descent.

    After checking the engine gauges and shutting the engine down, a pilot should establish best glide first, not nose down and descend at a high rate trying to make an airport.  Best glide gives the pilot many more options and a lot more altitude to work with, further allowing him/her to plan how to make an airport directly underneath the airplane.

    To pontificate, it seems that if the pilot had adjusted the plane to best glide, instead of performing an emergency descent, there is the possibility that Drake Field would have been reachable, the chute would not have been needed, and the driver of the truck would not have had to visit the hospital.  Hindsight is 20-20, but this may be an overall training and decision making issue that may need further emphasis.

    The initial NTSB report as well as a link to the CBS story is below.

    http://www.cbsnews.com/live/video/pilot-forced-to-deploy-emergency-parachute-in-arkansas/

    NTSB Identification: CEN16LA026
    14 CFR Part 91: General Aviation
    Accident occurred Tuesday, November 03, 2015 in Fayetteville, AR
    Aircraft: CIRRUS DESIGN CORP SR22T, registration: N857SW
    Injuries: 3 Minor, 1 Uninjured.
    This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.
    On November 3, 2015, at 0950 central standard time, a Cirrus SR22T airplane, N857SW, descended under the canopy of the cirrus airframe parachute system (CAPS) and landed on a road in Fayetteville, Arkansas. The pilot, pilot rated passenger and one person on the ground received minor injuries. One passenger in the back right seat was uninjured. The airplane was substantially damaged. The airplane was registered to WG Aviation LLC, Rogers, Arkansas, and operated by a private individual under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed at the time of the accident and an instrument flight rules (IFR) flight plan was filed. The flight departed from the Bentonville Municipal Airport (VBT), Bentonville, Arkansas, at 0934 and was en route to the Waco Regional Airport (ACT), Waco, Texas.

    According to the pilot, after departure from ACT he leveled off around 10,000 ft mean sea level (MSL) and was in “VFR on top” conditions. The pilot noticed that the crew alerting system (CAS) flashed a yellow caution light for oil pressure; the engine was still producing power. The pilot notified air traffic control (ATC) of the issue and received vectors to the nearest airport, Drake Field Airport (FYV), Fayetteville, Arkansas. The pilot descended and maneuvered toward FYV as the CAS indicated a red warning light for oil pressure, which had dropped below 10 psi. The engine was producing inconsistent power as the airplane descended to 3,300 ft and FYV was still not in sight due to cloud coverage. The pilot was unable to maintain altitude and the airplane’s stall warning horned sounded. The pilot deployed the Cirrus airframe parachute system (CAPS) and descended to the ground. During the landing the airplane collided with a truck and then came to rest on a four lane road.

    At 0953, the weather observation at FYV reported wind from 190 at 9 knots, gusting to 17 knots, 10 miles visibility, clear sky, temperature 61° F, dew point 57° F, and altimeter setting 30.11 inches of mercury.

    An initial postaccident examination was conducted on November 4, 2015, in Fayetteville. Engine oil was observed on the underside of the fuselage. The oil cooler cross fitting was broken and oil was observed in the engine compartment.

    The airplane’s recoverable data module and three data cards were removed and sent to the NTSB Vehicle Recorders Laboratory for download.

    The airplane has been retained for further examination.

  • Dallas Airspace Changes

    As was the case with the Class B Airspace around Houston several months ago, the Class B Dallas airspace has been overhauled as well.  These changes were implemented at the last database update on September 18th.  If you’ll be flying into any of the Dallas airspace airports IFR, make sure you have current charts and your GPS databases are updated.

    According to AOPA, 14 SIDs and STARs were deleted, a number of new procedures were added, and changes were made to most of the other remaining procedures.  The new procedures in the Dallas airspace consist mainly of RNAV procedures for turboprops and jets, so most GA aircraft won’t be affected by those.  The legacy procedures that remained in place over went changes, including new frequencies, so piston aircraft going into the Dallas airspace are still affected.

    From AOPA, departures from Dallas Love (KDAL) that file their flight plan with special equipment /G in their flight plan will automatically be given an RNAV departure procedure.  This does not appear to affect piston aircraft as all the new RNAV SIDs in the Dallas airspace are for turboprops or turbojets.

    The reason for the changes to the Dallas airspace?  Similar to the changes in Houston, these airspace changes are meant to streamline departures and arrivals in the Dallas airspace area, reduce controller workload, and give continuous descent angles for arriving high altitude traffic.

    Don’t be surprised the next time you are in the Dallas airspace area if you receive a clearance that states:  “Descend via the arrival.”  In that case, just check the chart and aim for the appropriate altitudes at the appropriate fixes.  As we move closer to the ADS-B requirement, I believe we will see more and more of these terminal procedure overhauls, so be prepared and keep those charts and databases up to date.

  • Avidyne Vantage

    For years, Cirrus owners who have the Avidyne Entegra PFD and MFD have been clamoring for Avidyne to come up with some sort of upgrade. The Entegra, or EX 5000 system, is late ’90s technology and, though it still works, there will be a certain point in the future when it gives up the ghost. Avidyne still supports the Entegra system, but it’s hard for a Cirrus owner to see all this new technology coming on the market while not being able to upgrade the original Avidyne screens.

    Avidyne gave it a go in the late 2000s with a panel upgrade known as the R9. The R9 was a good system, but Avidyne was very slow on the release (rumors were the company wanted it to be absolutely perfect before releasing it, which frustrated Cirrus, who then switched to the Garmin Perspective panel, leaving Avidyne behind) which led to the R9 only being available as a very expensive retrofit to the Entegra system ($80,000-$90,000 for the system and install). Needless to say, there weren’t that many takers.

    Late in 2020, Garmin announced it had received certification to retrofit Avidyne Entegra equipped Cirrus Aircraft with the company’s G500 TXi displays, which gave new hope to G1, G2, and G3 Cirrus owners. The price tag wasn’t outrageous, coming in at $16,000 apiece for each display. The G500 TXi works with any possible GPS that can be installed in a Cirrus (GNS 430Ws, GTN 650s, GTN750, or the Avidyne IFD 540/440) and with the DFC 90 Autopilot (if the Cirrus is still equipped with an STEC 55x, the Autopilot would need to be changed to either a DFC 90 or a Garmin GFC 500).

    Fast forward to June of 2021 and Avidyne re-enters the game with the Avidyne Vantage. After the R9 debacle, Avidyne has opted this time to go for a more simple approach. The Avidyne Vantage system changes out the Entegra PFD and MFD with bigger screens (12″; Garmin’s TXi units are only 10.6″) with high quality pixelation, synthetic vision, engine gauges, checklists, charts, a hybrid touch interface, and all the other information that was offered on the Entegra system, just all more modern and updated. The best news is that the system provides redundant reversionary mode, which was one of the biggest complaints about the Entegra system.

    The price tag comes in lower than Garmin, with each screen being priced at $12,500. The units will work seamlessly with the Avidyne IFD Series GPS units, though, as of this writing, it isn’t clear if the Avidyne Vantage will work with Garmin GTN 430Ws or the GTN 750/650. I would assume that the integration would be there, but I haven’t found any documentation stating that yet. DFC 90 Autopilot integration would be seamless, but not sure the integration with the STEC 55x or Garmin GFC 500.

    Avidyne says the Vantage will be fully certified in early 2022, but the company is taking orders now. Visit the Avidyne Website for more information.

  • The Go Around Button

    Back in the old days, when flying an approach in an early Cirrus SR22 (circa 2004; yes, in airplane technology, those were the old days), performing a missed approach procedure was a lot of work.  You were low to the ground and weren’t able to see the runway.  Then, you had to start climbing so you don’t hit the ground, then push a lot of buttons in order to get the GPS and autopilot set fly the missed approach procedure.  It was very easy to get distracted with button pushing, then forget to fly the airplane, putting yourself and passengers in very unsafe circumstances.  The go around button has changed all that.

    Going Missed the Old Fashioned Way

    Let’s stick with our example of the 2004 Cirrus.  The SR22 in 2004 was equipped with the Avidyne Entegra system, complete with dual Garmin 430 GPS units, and an STEC 55x Autopilot.  A very capable IFR flying machine (we could use the same example of a 2004 or 2005 Lancair Columbia 350 or 400 that was equipped the same way, except the screens were vertical instead of horizontal).

    Avidyne Cirrus Go Around Button

    We’ll use the ILS 15 at the Temple airport, KTPL, for our example.  You pass TPL, the outer marker at 1,683 with the glide slope already centered.  Everything is going well so far.  The number 1 Garmin 430 is set to VLOC and the autopilot is showing NAV and APR for the lateral guidance and GS on the vertical, tracking the glide slope.  The last weather report stated the clouds were Broken at 500 feet, so it appears like you’ll be able to get in on the approach.

    As you get closer to the Decision Altitude, the clouds aren’t letting up at all.  You hit 1,000 feet on your altimeter, 120 feet above the minimums, and you still can’t see a thing.  Another 100 feet lower doesn’t change anything, so you elect to proceed with the missed approach.  This means things are about to get busy.

    Here’s the process:

    • Fly the airplane first, meaning shut off the autopilot, pitch the nose up to about 7 degrees, TRIM, add full power, retract the flaps, and step on the right rudder
    • The Garmin 430 is now in SUSP mode, meaning the missed approach point is locked in as the active waypoint.  So, you have to press the OBS button to cause the GPS to cycle over to the missed approach procedure
    • You have to press the VLOC button on the Garmin 430 in order to change the CDI back to GPS
    • You have to re-engage the autopilot by pressing NAV twice (which engages GPS Steering mode)
    • You have to reset your altitude bug (if you hadn’t set it for the missed approach altitude previously)
    • You have to press VS and ALT on your autopilot to have the STEC continue the climb

    That’s a lot of work, isn’t it?  Plus, that’s an extensive amount of head down time in the cockpit, with your eyes looking elsewhere other than the instruments while hand flying.  All very low to the ground, I might add.  Can you see how this can be dangerous?  (Note:  The Avidyne IFD 550 has made this a little easier with automatically switching from VLOC to GPS and automatically engaging the missed approach procedure in the flight plan)

    The advent of the Go Around Button has streamlined the process, leading to safer operations where it matters most.  The functions of the Go Around Button vary based on the airplane, but here are three examples, the Garmin G1000 Cessna Corvalis TT, the Garmin G1000 Piper Mirage, and the Garmin Perspective Cirrus SR22.

    Cessna Corvalis TT

    We’ll take the above situation and swap out the airplanes.  Gone is the 2004 Cirrus SR22.  Insert a 2008 Cessna Corvalis TT, equipped with the Garmin G1000 suite and the GFC 700 autopilot.  The go around button is positioned directly above the twist in throttle.

    Cessna Corvalis G1000 Go Around Button

    When you push the Go Around Button, here’s what the system does:

    • Disconnects the Autopilot
    • Sets the Flight Director for 7.5 degrees pitch up (which is about your normal climb angle) and wings level
    • Switches the CDI back to GPS
    • Takes the GPS out of SUSP mode and cycles the flight plan to the first waypoint on the missed approach procedure

    Here’s what you have to do:

    • Follow the flight director by pitching the nose up and TRIM
    • Add full mixture, prop and throttle (prop & throttle should be full already)
    • Retract the flaps
    • Step on the right rudder
    • Re-engage the autopilot, then press NAV and VS (or FLC) and set your altitude bug if it isn’t already set

    Not too bad, eh?  Makes the whole situation streamlined and safer.

    Piper PA46-350P Mirage

    Same situation, different airplane.  You’ll notice the procedure for the Piper Mirage is almost exactly the same as the  Corvalis procedure.  The difference between the two airplanes is where the autopilot controller is.  In the Corvalis, the autopilot controller is positioned on the left side of the MFD, making it easy to scan back and forth while pushing buttons on the autopilot.

    The Piper Mirage autopilot controller is positioned below both screens and in front of the power quadrant. With this positioning, the pilot’s eyes have to go a lot further to see which autopilot button he is pushing. In this case, it becomes very important to get the airplane climbing and trimmed before going down to engage the autopilot.

    As in the Corvalis, here is what the Go Around button does:

    • Disconnects the Autopilot
    • Sets the Flight Director for 7.5 degrees pitch up (which is about your normal climb angle) and wings level
    • Switches the CDI back to GPS
    • Takes the GPS out of SUSP mode and cycles the flight plan to the first waypoint on the missed approach procedure

    And here’s what you have to do:

    • Follow the flight director by pitching the nose up, then TRIM
    • Add full mixture, prop and throttle (prop & throttle should be full already)
    • Retract the flaps
    • Step on the right rudder
    • Re-engage the autopilot, then press NAV and VS (or FLC) and set your altitude bug if it isn’t already set

    Cirrus SR22

    Cirrus Perspective Go Around Button

    This time, we’ll use the 2010 Cirrus SR22T with the Garmin Perspective and GFC 700 Autopilot. One thing I really like about how Cirrus configured their system is where the Go Around button is.  It’s actually on the throttle itself, making it much more intuitive.  This way, you can press the Go Around button while adding full throttle.

    There is one major difference between the Garmin Perspective in the Cirrus and the G1000 in the Corvalis. When you press the Go Around button in the Cirrus, the autopilot actually stays on.

    Here’s what happens when you press the Go Around button in the Cirrus:

    • Flight Director pitches to 7.5 degrees pitch up and wings level
    • AP Mode switches to Go Around mode, following the flight director
    • GPS comes out of SUSP mode
    • CDI switches back to GPS

    All the pilot really has to do is add power, take the flaps up, then press NAV on the GFC 700 to get the autopilot following the missed approach procedure.

    If you aren’t familiar with the Go Around button or haven’t used the one in your plane lately, it’s good to go up with a knowledgeable instructor and fly a couple of approaches where you perform the published missed approach afterward.  That way, he or she can assist you through the first missed approach, then give you pointers until  you get comfortable with the Go Around button.

Leave a Reply

Your email address will not be published. Required fields are marked *