Home       Features       Site Map      Français

Arrow
Arrow
Slider

Issue 01-2014

back-to-asl-button  download-asl-button

Night IFR Approach in IMC Claims IFR-Rated Private Pilot and Passenger

The following article is based on TSB Final Report A11O0239—Loss of Control—Collision with Terrain. This accident in Ottawa, Ont.,
took the lives of two local pilots and received a lot of media attention. The TSB report is a very compelling read for all of us, but particularly
for IFR-rated private pilots or soon-to-be IFR-rated private pilots.

Summary

On December 14, 2011, a privately owned Cessna
177A Cardinal departed Wilkes-Barre Wyoming Valley
Airport (KWBW), Pa., USA, with two persons on board, on
an IFR flight plan to Ottawa/Carp Airport (CYRP), Ont.
Approximately 44 NM from destination, because of low
visibility and ceilings at destination, the aircraft diverted to
its filed alternate of Ottawa/Macdonald-Cartier International
Airport (CYOW), Ont. The aircraft was then cleared for an ILS
approach to Runway 07. At about 19:12 (all times quoted are
EST), while flying the approach in instrument meteorological
conditions (IMC) at night, the aircraft collided with the ground
approximately 1.9 NM west of the threshold of Runway 07. The
aircraft was destroyed, and both occupants were fatally injured.
There was no fire. The 406 MHz ELT activated on impact.

Wreckage of Cessna Cardinal 1.9 NM west of the threshold of
Runway 07at CYOW

History of the flight

The aircraft was returning to CYRP from a 12-day trip to
southern Florida and the Bahamas. Both persons on board
were licensed pilots and generally shared the flying duties
throughout the trip.

On December 13, 2011, the two pilots checked out of their
hotel at 07:00 and departed Marsh Harbour International
Airport (MYAM), Bahamas, at 09:57 for Newport News/
Williamsburg International Airport (KPHF), Va. The flight
consisted of three stops and 10.5 hr of flight time, arriving at
KPHF at 00:16 on December 14, 2011. The pilots checked
into a hotel at 00:55.

At 12:15 on December 14, 2011, the aircraft departed KPHF and
arrived in Wilkes-Barre Wyoming Valley Airport (KWBW), Pa.,
at 14:51. At approximately 17:07, after civil twilight, the
aircraft departed KWBW on an IFR flight plan destined for
CYRP. At 18:40, approximately 44 NM south of CYRP, the
pilot-in-command (PIC) requested a diversion to CYOW for
a Runway 07 ILS approach. CYOW is located 15 NM east of
CYRP. An ILS approach is unavailable at CYRP.

At 19:06, Ottawa Terminal ATC cleared the aircraft for the ILS
approach to Runway 07 and issued radar vectors to intercept
the final approach course. The aircraft intercepted the localizer
approximately 8 NM from the threshold, and the terminal
controller instructed the aircraft to contact the Ottawa tower
controller. The tower controller informed the aircraft that it
was number one in the landing sequence. At approximately
4.5 NM from CYOW, while on the ILS approach, the aircraft
began to deviate north of the localizer. The tower controller
informed the pilot of the deviation. The pilot acknowledged
the information and informed the tower controller that they
were trying to get back on track. A minute later, as the aircraft
was approaching the centre of the localizer, the tower controller
cleared the aircraft to land. Shortly after receiving the landing
clearance, the aircraft began to deviate northbound again; the
controller informed the pilot of the deviation. There was a
brief, unrecognizable transmission on the tower frequency, but
it could not be confirmed that it came from the Cessna 177.
Eighteen seconds later, the controller instructed the aircraft to
pull up and go around. There was no response.

At approximately 19:12, the aircraft entered a steep right turn
with a rapid descent, and struck power lines before impacting
the ground 1.9 NM west of the threshold of Runway 07. Radar
data show that, while on the approach, the aircraft twice deviated
significantly from the localizer to a point that would have caused the
localizer indications on the aircraft instruments to go to full deflection.
Airspeed on the approach was maintained above 100 kt until the
loss of control (Figure 1).

Figure 1—Aircraft’s flight path showing its deviations from the localizer
during the final approach.

Weather and flight planning

At 16:21, while on the ground at KWBW, the PIC filed an IFR
flight plan with Williamsport flight service station (FSS). The
flight was planned to depart at 17:00 and cruise at 5 000 ft, and
was estimated to take 2 hr and 10 min to CYRP. The alternate
airport for the flight was CYOW; the forecast weather was
within alternate limits at the time of filing.

When the pilot called the FSS to file the flight plan, a weather
briefing was not requested. It could not be determined if the
pilot accessed the latest weather reports on the Internet prior
to the flight-plan phone call. The flight service specialist asked
if the pilot wanted information relating to icing and proceeded
to inform the pilot of an AIRMET that forecast moderate
icing between 3 000 and 14 000 ft on the flight route. The
pilot asked about the area around Watertown, which was on
the flight route, and the flight service specialist indicated that
there were no pilot reports, but that they might encounter some
showers as indicated by the AIRMET.

The latest forecast weather available for CYOW at the time that
the flight plan was filed was issued at 15:38. Forecast conditions
at 18:00 were visibility greater than 6 SM, scattered cloud at
1 500 ft and broken ceiling at 4 000 ft. Between 18:00 and
20:00, the conditions were forecast to deteriorate temporarily
to visibility of 2 SM in mist and ceiling at 900 ft overcast. At
20:00, conditions were forecast to improve to visibility greater
than 6 SM in light snow and rain showers with overcast ceilings
at 3 000 ft.

The latest actual weather at CYOW at the time that the flight
plan was filed was issued at 16:00. It described conditions as
wind 090° at 8 kt, visibility 3 SM in mist and ceiling overcast
at 700 ft.

At 18:12, while cruising at 5 000 ft, 29 NM south of
Watertown International Airport (KART), the pilot requested
a weather update for KART and CYOW from Boston Flight
Watch (BFW). The BFW specialist reported conditions at
KART to be visibility 10 SM and overcast ceilings at 9 500 ft,
and conditions at CYOW to be visibility 3 SM in mist and
overcast ceiling at 200 ft. The specialist repeated the AIRMET
previously described, and the PIC indicated that the crew would
check for updates once the aircraft was across the border.

At 18:34, while crossing the Canada–USA border near
Gananoque, Ont., the pilot requested a weather update for
CYOW from Montréal ATC. The weather relayed was the
same as previously reported by BFW. Six minutes later, the
pilot asked to change the destination to CYOW.

At 19:06, before clearing the aircraft for the ILS approach,
Ottawa Terminal ATC issued the latest weather to the pilot:
ceiling at 200 ft AGL, visibility 3 SM in mist and wind 100°
at 10 kt gusting to 15 kt.

The aircraft

The aircraft was certified, equipped and maintained in accordance
with existing regulations. Examination of the aircraft wreckage
determined that there were no signs of pre-impact damage or
defects that would have precluded safe flight. The aircraft was
not certified for flight into known icing conditions and did not
have any anti-ice equipment other than a heated pitot tube.

The aircraft collided with the ground with the flaps selected
up. In this configuration, the Cessna 177A stall speed is listed
in the owner’s manual as 57 kt.

The pilot and passenger

The PIC held a private pilot licence, a valid Category 3 medical
certificate and a valid Group 3 instrument rating. The pilot’s
personal logbook, last completed prior to the return trip,
contained the following totals (hr):

  • Total flying time 429.1
  • Night flying as PIC 30.3
  • PIC on the accident aircraft 28.7
  • Actual instrument 44.1
  • Simulated instrument (hood) 40.9
  • Simulator 41.8


While the logbook showed a total of 44.1 hr of actual instrument
time, the TSB determined that this column was being used to
record time spent flying on IFR flight plans rather than time
spent in actual IMC. Analysis of the departure, arrival and en
route weather of these recorded flights suggests the pilot had
experienced very little, if any, actual flight in IMC.

Canadian Aviation Regulation (CAR) 401.05(2)(b)(i)(B) requires
a pilot who is carrying passengers at night to have completed
five night takeoffs and five night landings in the preceding six
months. Records indicate that the PIC had completed only one
takeoff and two landings at night in the prescribed time period.

The passenger held a private pilot licence and a valid Category
3 medical certificate. Records indicate that the passenger had

approximately 330 hr of experience, including 58 hr at night
as PIC and 5.9 hr under simulated instrument conditions. The
passenger did not possess an instrument rating.

Flight tests

Flight tests in Canada are evaluated using a 4-point marking
scale. A detailed explanation of the marking scale is outlined in
the Flight Test Guide—Instrument Rating published by Transport
Canada (TC), but the following applies in general:

  • 4 – Performance is well executed considering
    existing conditions.
  • 3 – Performance is observed to include minor errors.
  • 2 – Performance is observed to include major errors.
  • 1 – Performance is observed to include critical errors,
    or the aim of the test sequence/item is not achieved.


The PIC had attempted 5 flight tests since beginning flight
training in 2003.

On May 5, 2005, the PIC completed a private pilot flight test,
which was assessed as a pass. On Exercise 24A: Instrument
Flying—Full Panel, the PIC received a mark of 2. The pilot
examiner noted that the candidate was “chasing the needle”,
referring to a series of over-corrections in an effort to regain
the desired track.

On October 26, 2007, the PIC completed an instrument-rating
flight test, which was assessed as a pass. On Exercise 8: ILS
Approach, the PIC received a mark of 2. The pilot examiner
noted that the candidate let the glideslope deviate to ½-scale
deflection inside the outer marker, because he was trying to read
the pre-landing checklist. The PIC was granted an instrument
rating valid to November 1, 2009.

On December 11, 2009, the PIC attempted an instrument rating
renewal flight test, which was assessed as a fail. On Exercise 2:
IFR Operational Knowledge, the PIC received a mark of 1.
The pilot examiner noted that the candidate was unable to
explain the approach ban and showed an unacceptable level
of knowledge. The flight test was stopped on the ground after
this exercise was failed.

On October 7, 2011, the PIC attempted an instrument
rating renewal flight test, which was assessed as a fail. On
Exercise 8: ILS Approach and Exercise 9: Missed Approach,
the PIC received a mark of 1. The pilot examiner noted that
the candidate let the glideslope deviate to full-scale deflection
and let the course deviation indicator deflect fully en route
to the missed-approach waypoint.

TC’s Flight Test Guide—Instrument Rating describes the aim,
description and performance criteria for each exercise to be
completed on the flight test. For Exercise 8 (ILS or LPV1
Instrument Approach [Precision Approach]), the Performance
Criteria section, (i), states that assessment will be based on the
candidate’s ability to, “on final approach course, allow no more
than ½-scale deflection of the localizer or glideslope indications”.

CAR Standard 421.49(4)(b) requires applicants renewing an
instrument rating that expired more than 24 months before
the date of application to rewrite the instrument-rating
written examination (INRAT). The original instrument rating
held by the PIC would have been expired for 24 months on
November 1, 2011.

On October 31, 2011, the PIC completed an instrumentrating
renewal flight test, which was assessed as a pass. The PIC
received a mark of 2 on 4 exercises, including Arrival, Holding,
RNAV Approach and ILS Approach. The pilot examiner noted
on the flight test report that the candidate let the localizer
deviate to ½-scale deflection upon interception. Notes written
on a separate piece of paper during the flight test described
the localizer deviation as ¾-scale. Had the most recent
instrument-rating renewal flight test not been completed, the
PIC would have had to rewrite the INRAT.



Factors affecting pilot decision making

The PIC had several work appointments that were scheduled
for the day following the accident. In addition, the pilot also
had personal commitments to attend to later that week.

In the Operators Guide to Human Factors in Aviation2 (OGHFA),
the Flight Safety Foundation (FSF) describes the phenomenon
of making a decision to continue to the planned destination
or toward the planned goal even when significantly less risky
alternatives exist. This phenomenon has been variously referred
to as “press-on-itis”, “get-home-itis”, “hurry syndrome”, “plan
continuation” and “goal fixation”3.

The FSF states that the following are some of the reasons that
aircrews may be susceptible to “press-on-itis”:

  • They have a personal commitment/appointment at the
    completion of the flight, or they may simply want to get to
    the destination.
  • They want to “just get the job done” (excessive commitment
    to task accomplishment) and are influenced by organizational
    goals such as on-time arrival, fuel savings and passenger
    convenience.
  • They focus solely on aircraft flight path control, due to
    turbulence and other distractions.
  • “We are almost there, let’s just do it and get it over with.”
  • They become task-saturated.
  • They are fatigued.
  • They lose situational awareness and are not fully aware of
    the potentially perilous situation.
  • They have not set performance limits and trigger gates that
    require a go-around.
  • They are not fully aware of their own limitations and/or the
    aircraft’s limitations.

Analysis

The PIC was appropriately licensed and instrument rated.
However, the most recent, and other, flight test reports showed
signs that the PIC had continued difficulty conducting ILS
approaches. In addition, the PIC was not current in night-flying
operations, and had very little, if any, experience in actual IMC.
Most of the PIC’s instrument-flying experience was acquired
during training in simulated IMC and in the simulator.

2 European Advisory Committee, Operators Guide to Human Factors
in Aviation. Flight Safety Foundation (2009), available at http://www.
skybrary.aero/index.php/Portal:OGHFA
(last accessed 25 October 2013)

3 European Advisory Committee, “Press-on-itis” (OGHFA Briefing
note), Operators Guide to Human Factors in Aviation, Flight Safety
Foundation (2009), available at http://www.skybrary.aero/index.php/
Press-on-itis_(OGHFA_BN)
(last accessed on 25 October 2013)

This experience may not have presented the PIC with an
accurate representation of the conditions and pressures faced in
actual conditions.

The PIC chose to depart KWBW into forecast icing conditions
despite the fact the aircraft was not certified for such operations.
While en route, the pilot was informed of deteriorating
conditions in the Ottawa area but chose to continue. This
decision and the previous day’s long flying schedule, combined
with work and personal commitments, suggest the PIC may have
been susceptible to the phenomenon known as “press-on-itis”.

While on the ILS approach into Ottawa in unfamiliar night
IMC, the pilot had significant difficulty maintaining the
localizer. During the approach, the tower controller twice advised
the pilot that the aircraft was deviating from the approach
course. During the second attempt to regain the localizer,
the pilot most likely made a steep right turn, which quickly
developed into a rapid descent and loss of control.

Airframe icing could not be completely ruled out as a possible
contributor to the loss of control, but the high airspeed (> 40 kt
above the stall speed) that was maintained until the loss of
control suggests that it was unlikely. Icing likely did not
contribute to the aircraft’s repeated deviation from the localizer
and over-correction.

Finding as to causes and contributing factors

1. During an attempt to fly the precision approach at night in
weather conditions unfamiliar to the pilot, control of the
aircraft was lost and the aircraft collided with the ground.

Findings as to risk

1. If pilots possess limited currency and experience at night
or in instrument flight conditions, the risk of a loss of
control is increased when operating an aircraft in marginal
weather conditions.

2. Non-recognition of the effects of the phenomenon known
as “press-on-itis” can lead to increased risk that a decision
will be made to depart or continue a flight when significantly
less risky alternatives exist.

Other finding

1. The pilot did not meet the recency requirements for night
flying with passengers.

This particular accident has created a lot of discussions in pilot lounges
as well as on various online aviation blogs. Thought-provoking issues
are addressed, challenged and debated. Such issues include the realities
and challenges of IFR training, IFR qualification for commercial
pilots as opposed to private pilots, giving and taking check rides,
passing and failing those check rides, the need for actual IMC time,
mentorship, IFR theoretical knowledge, pressure and the insidious
effects of fatigue. While briefly mentioned in the report under “Factors
affecting pilot decision making”, one has to wonder whether fatigue
could have been a contributing factor in this accident. Read again
the pilots’ schedules described in the report for December 13 (over
17 hours) and December 14 (close to 8 hours). Combined with very
poor weather and the pressing desire to get home, the cumulative
effects of fatigue may have played a role in this accident. Want to
learn more from this accident and others? Hit the blogs, but check
your feelings at the door. —Ed.

-

Issue 01-2014

back-to-asl-button  download-asl-button

COPA Corner: Flight Through Thunderstorms is Asking for Trouble

by Donald Anders Talleur. This article was originally published in the October 2010 issue of COPA Flight under the “Pilot’s Primer” column.

I write this article shortly after Flight 8520, an AIRES
Boeing 737, crashed while on approach to San Andres Island,
a Colombian resort area. While the investigation of this crash
is still ongoing1, I feel compelled to focus on one prominent
circumstance that could have played a role in bringing this
aircraft to the ground prematurely.

According to all reports, Flight 8520 was flying through a
thunderstorm during the approach to landing. While I do not
intend to speculate on the particulars of this crash, its occurrence
is a reminder that there are inherent dangers in attempting to
fly through a thunderstorm, and it is those dangers that I’d like
to address this month.

Thunderstorms contain some of the scariest weather known to
man, and the danger of that weather is well known.
Wind shear, microbursts, hail, lightning and turbulence are the
main hazards and exist in thunderstorms to varying degrees
depending on the size and strength of the storm. I should
point out that size and strength are generally synonymous in
that a storm with very high tops is also generally capable of
producing the worst weather.

Although wind shear and microbursts can occur independently
of a thunderstorm, as “painted” on the radar, those associated
with a thunderstorm frequently produce the most hazardous
flight conditions.

There are a slew of accident cases that list wind shear/probable
microburst as contributing to the ensuing loss of control. The
typical situation is that an airplane gets into a wind shear
situation close to the ground during approach to landing.
A sudden shift in headwind component means a loss of
indicated airspeed.

On final approach, the margin between indicated and minimum
1 The final occurrence report into the AIRES Flight 8520 accident has
been released by Colombian authorities since the original publication
of this article. The probable cause of the accident was: “Execution of the
flight below the angle of approach, due to a misjudgment of the crew,
believing to be much higher, leading the aircraft to fly a typical trajectory
of a ‘black hole’ illusion, which was experienced during the night-time
approach to a runway with low contrast surrounded in bright focused
lights, aggravated by bad weather of heavy rain.” (from the Aviation
Safety Network’s Web page on Flight 8520)

safe flying speed is small, so any sudden loss of airspeed often
signals the need for immediate action on the pilot’s part.
Failure to react quickly can result in a stall or even premature
ground contact. Typically, wind shear close to the ground
does not exceed 20 kt, so it can usually be “powered” out of.
That being said, if a report for wind shear exists, extreme
caution should be taken when attempting a landing in
such conditions.

If wind shear is encountered during landing or takeoff, the
airspeed loss or gain and the altitude of occurrence should be
reported to ATC.

While wind shear is relatively common, a less common type
of wind shear event is the microburst. If there can be a worstcase
wind shear scenario, I’d have to say that a microburst is
it. Years ago, I saw what a microburst could do when one hit a
small airport northwest of the Chicago, Ill. area.

The damage was amazing. If it hadn’t been classified as a
microburst, I might have suspected a mini-tornado. Tied down
airplanes were uprooted, and one was even found upside down
on top of a nearby hangar. A nearby barn was flattened. Now
picture yourself trying to fly through something that could do
all of that!

Several airliners have tried over the years and failed miserably.
An L-1011 crash at Dallas/Fort Worth a bunch of years ago
was tragic testimony that a microburst can bring down the
largest of aircraft.

Since then, some pretty smart folks in the U.S. have looked
into the microburst phenomenon and made startling findings.
They found that microbursts are a whole lot more common
than anyone had previously thought.

Through the use of sophisticated measuring equipment they
mapped out microburst activity at and near major airports across
the U.S. and came to the conclusion that microbursts are possible
anywhere there is convective activity (i.e. thunderstorms).

Although many microbursts were of an intensity that a large
airplane might make it through, many more were of an intensity
greater than what brought down that L-1011. While I won’t go
into the gory details of how a microburst works in this article,
it’s clear that the name of the game is to avoid microbursts
in the first place. The best way to do that is to stay away
from thunderstorms.

Another hazardous feature of thunderstorms is turbulence.
Although generally brief, turbulence in a thunderstorm can be
quite violent. The combination of updrafts, downdrafts, swirling
and shifting patterns of air within a thunderstorm can lead to
turbulence that is too difficult for even a jetliner to traverse.

Case in point, just today there was news of a jetliner on the east
coast of the U.S. that diverted for landing after encountering
severe turbulence in or near a thunderstorm. This is exactly
the type of weather event that should be avoided if possible.

However, the major difficulty in avoiding turbulence is due to
the difficulty of accurately predicting its whereabouts. Luckily,
with the advent of Doppler radar, air currents likely to produce
turbulent conditions are more easily identifiable. Still, air current
activity in a thunderstorm changes frequently, making precise
predictions impossible.

As a result of the somewhat stealthy nature of turbulence, as a
general rule, expect it anywhere near or within a thunderstorm.

One inevitability is where there’s a thunderstorm, there’s
lightning. This point is academic since to have thunder there
must be a preceding bolt of lightning. Lightning is rarely accused
of bringing down airplanes these days (although it has happened
and will probably happen in the future) owing to advances
in the bonding of aircraft structures to facilitate the better
distribution of the charge and subsequent discharge back into
the air. At worst, airliners generally suffer nonstructural issues
such as nose cone or wing tip damage, but there have been a
few suspected cases where a strike led to a fuel tank rupture
and tragic results.

Newer aircraft with composite structures present new problems
in that a strike can lead to delamination of material near the
strike zone as well as the conventional damage expected at the
discharge point(s). Since there is really no way to know how a
given aircraft will react to a strike, the best solution is to stay
at least 10 mi. clear of thunderstorms. Why so far, you might
ask? Simple! Lightning need not stay in the cloud, and if your
airplane is a convenient object to attract the strike, then…
tag—you’re it!

One last serious hazard, as if the others weren’t bad enough
already, is hail. Imagine your friend throwing ice cubes at you
from a distance of 10 ft. It probably won’t kill you, but if he
throws them hard enough, expect some small bruises. Now
imagine him throwing those cubes at you at 200 kt. Ouch!

A jetliner flying through hail won’t “feel” much better, and
the Internet is full of interesting pictures of damage caused
by relatively short encounters with hail. Busted or completely
shredded nose cones, busted windshields, leading edge damage
that will make you think the airplane flew through a baseball
factory; these are serious problems to be sure.

The damage to a small airplane can be equally as bad even
though the speed is usually much lower. Slower aircraft
will be slower to exit the hail and that means more time
for damage.

So how does a pilot avoid hail? Well, for starters, never fly under
anything that looks like the anvil of a thunderstorm, and also
don’t fly through the vertical thunderstorm cloud. Although
hail falls in relatively predictable areas of a storm, a pilot does
not generally have the information available during flight to
select the right path. Also, although you might fly in the clear
air below an anvil, it may be difficult or impossible to spot hail
falling prior to running into it.

If I’ve scared you enough to keep you out of thunderstorms then
I’d say this article has been a success. These weather phenomena
are serious hazards to all aircraft and should be avoided at all
costs. Don’t believe that just because someone you know made
it through a storm, that it’s possible to do so on a regular basis.

The only way an airplane makes it through a full-blown
thunderstorm unscathed is by luck. Don’t get me wrong, luck
is good, but if you’re not the type to gamble your entire life
savings on a card game, then you might just want to wait out
that thunderstorm. The odds of winning the card game are
probably better than winning a bout with a thunderstorm.

This month’s Pilot Primer is written by Donald Anders Talleur,
an Assistant Chief Flight Instructor at the University of Illinois,
Institute of Aviation. He holds a joint appointment with the
Professional Pilot Division and Human Factors Division. He has
been flying since 1984 and, in addition to flight instructing since
1990, has worked on numerous research contracts for the FAA, Air
Force, Navy, NASA and Army. He has authored or co-authored over
200 aviation-related papers and articles and has an M.S. degree in
Engineering Psychology, specializing in Aviation Human Factors.

-

Issue 01-2014

back-to-asl-button  download-asl-button

Know the Tin You're In

The following article was originally published in Issue 3/2002 of Aviation Safety Vortex and is republished for its enduring value as a
safety promotion tool. It should also be pointed out that its message applies to aircraft of all persuasions, not exclusively helicopters.

We often hear about the dangers of complacency and over the
years it’s been the subject of countless articles and accident
profiles. Usually, the focus of these discussions is on a lack of
diligence stemming from familiarity with a task—like flying
the same aircraft everyday on the same job. There are other
facets to our business, however, which also demand careful
attention to detail.

Often, helicopter pilots fly more than one helicopter, and are
expected to stay current on several types or models. These skills
develop as we gain experience, but the differences between
aircraft, even within the same type, can bite you if you’re unaware.

Helicopters, like most machines, are in a constant state of
change as manufacturers or operators learn from experience,
upgrade, or modify to suit operational needs. This can run the
gamut from the simple placement of switches to fitting engines
from different manufacturers.

Some examples:

  • Manual cargo releases may be cyclic or collective mounted,
    T-handles, or floor pedals. Even within the same type, like
    the AS350 series, the release may change depending on
    which hook is installed.

 

  • Power instruments—we have percent torque, PSI torque,
    pitch angle, differential Ng, first limit indicators, etc.
  • Rotor tachs—percent Nr vs. actual RPM.
  • Fuel gauges—pounds vs. percent vs. Gallons vs. Litres.
  • Many operators change cyclic heads, or the location of Force
    Trim Release, NAV Standby or Cargo Release buttons.
  • Some IFR platforms like the Sikorsky 76 series has almost
    as many avionics configurations as there are helicopters.
  • Emergency floats can be activated by buttons on the
    collective, triggers, or handles, depending on the installation.


You get the picture. When new to a machine, or when a variety
of different aircraft are flown, it is very important to familiarize
oneself with each ship. Failure to do so often results in forgotten
fuel valves, generators, cross feeds, rotor brakes, or dropped sling
loads during normal operations, and can cause critical delays
and mistakes when confronted with an emergency. That extra
few minutes you take to get acquainted could be the start of a
lasting friendship.


-

Issue 02-2014

back-to-asl-button  download-asl-button

A Good Flight Plan May Be Your Saving Grace

by Captain Jean Houde, Aeronautical Coordinator, Joint Rescue Coordination Centre Trenton

Our last contribution to this newsletter covered the close relationship between your ELT and the SAR system, more specifically the abundance of false alarms mainly due to beacon mishandling.

To reduce the rate of false ELT alarms, our recommendation was for all aircrew to dial 121.5 MHz on their radio prior to shutdown, notify ATC as soon as they notice an inadvertent activation and very seriously consider purchasing a 406 MHz beacon if they have not already done so. Strangely enough, we have noticed a slight reduction in such incidents over the last year. Is the message getting through?

In this issue, let’s focus on the number two cause of SAR system activation: the flight plan. The flight plan is sometimes filled out in haste and with little thought as to how crucial it may become a few hours later. But aviators should realize that it circulates deep within NAV CANADA after it is submitted.

Once a VFR or IFR flight plan is activated, it remains open until you close it through an ATC agency at your arrival aerodrome. If a flight plan is not closed within 60 min, it is categorized as an overdue aircraft situation which activates the SAR system. When that happens, many people and agencies are pulled into the picture including ATC, the Joint Rescue Coordination Centre (JRCC), local police and airport operators.

The JRCC aeronautical coordinator is notified the moment an aircraft is deemed overdue and creates a new SAR case file, which entails initial search planning and mission coordination.

Preliminary investigation work includes ramp checks at the departure and arrival airports, often conducted by local police in the middle of the night. Emergency contacts are notified, the flight plan is analyzed, the route is verified, possible alternates are considered, weather throughout the proposed flight ascertained, a communication search is conducted and so on.

If the situation cannot be resolved quickly, SAR resources are tasked to commence the search.

When you complete your flight plan, it is vital that the route you file is accurate. Deviations from your filed plan are made at your own peril because, should you run into trouble, your flight plan indicates where we begin our search.

If you must deviate from your flight path, report to ATC directly or via relay through any passing aircraft above you. The crew of a commercial airliner at FL410 will hear your transmission up to 250 NM away because they monitor 121.5 MHz. Providing regular reports to ATC along your route will help us to determine how far you have progressed along your track. This information will ultimately help us better focus SAR assets and increase your chances of being found sooner.

Unlike the old days of watch-map-ground, most pilots rely on GPS to take them safely to destination so we tend to find most missing aircraft in close proximity to the filed track.

 

Always use Zulu time instead of local time to mark your departure. Pilots often use local time which can cause considerable confusion. Be precise in calculating your endurance as it helps us determine how far you could have flown and ultimately determines the size of the search area.

Do not list yourself as the emergency contact if you are the one flying the aircraft. Ensure that your emergency contacts can be reached and have information regarding your whereabouts and/or your aircraft.

Once safely arrived at destination, remember that no job is finished until the paperwork is done. Make sure your flight plan is closed and check your ELT before shutdown. Tie a string on your thumb, if you have to, as a reminder before you leave the hangar and head home.

Even though it is not mandatory to file a flight plan when you fly within 25 NM of an aerodrome, let a responsible person know where you are going and have them call the JRCC or any ATC agency should they feel uneasy regarding your whereabouts. A 25-NM radius around an aerodrome is a larger search area than you think. In the absence of a flight plan with a clear proposed route, we have to search in ALL directions from the aerodrome and as far as your endurance can possibly take you. Imagine the size of the search!


Prepare for the elements

No one expects to spend one or several nights in the wilderness after taking off. But it happens, so you should be prepared. Dress for the occasion and in accordance with the outside weather in the region you are flying; bring survival gear, warm clothing, signaling equipment, matches, non-perishable food, water, etc. Since everyone carries a cell phone these days, carry yours with a full battery and leave it on throughout the flight. You would be amazed how many search areas were significantly reduced simply through cell phone pinging.

Better yet, because cell phones can be so helpful in resolving cases, bring a spare charged battery with you. Stay with the aircraft unless it puts you in danger; too many people walk away and this makes it even more difficult to find them. If your radio still works, make regular broadcasts on 121.5 MHz. If you can, start a fire and keep it going during the night. A fire stands out for many kilometres when seen from the air.

If you are in distress, ensure your ELT is activated—keep it activated until you are safely rescued. Leaving your beacon on even after you’ve been spotted by air is one more way you can help us help you.

All this to say: please be diligent in completing your flight plan, provide us with a means to contact a responsible person who can give us answers, stick to your filed route, expect the unexpected and call ATC after you land. The SAR service is here for you, but we need your help to find you in the most expeditious way. Safe flying!

 

-

Self-Paced Recency
Aviation Safety Newsletter
Emergency Operations
Smart Pilot Seminars
Features
Drones
General Aviation Safety
AOPA Flight Training
Ask ATS
Winter Flying
Fuel Management
Float Planes
Upset Training
Fit to Fly
ELTs
SAR

Pilot Resources

Ask ATS

Ask ATS

Have questions about ATS? In partnership with NAV CANADA, SmartPilot.ca is getting you answers!

Read More

Weather

Weather

Do you have the proper weather to fly? View local and national forecasts.

Read More

TSB

TSB

The Transportation Safety Board is an independent agency that advances transportation safety by investigating occurrences.

Read More

Interactive

Interactive Materials

Check out SmartPilot's online courses and other interactive learning materials.

Read More

NOTAMs

NOTAMs

Check out the latest NOTAMs from NAV Canada.

Read More

ASI

Air Safety Institute

Browse through ASI's free safety education and research designed to make you a better pilot from home!

Read More

ELTs

ELTs

Learn about the next generation in SAR.

Read More

ASL

Aviation Safety Letter

Articles include aviation safety, safety insight derived from accidents & incidents, safety information.

Read More

SmartPilot proudly works with.

aopa logocopa logoeaa logo

sar logo

We would like to acknowledge the financial support of the Government of Canada for this initiative through the Search and Rescue New Initiative Fund (SAR NIF).