Echo, Inc. v. FAA
This text of Echo, Inc. v. FAA (Echo, Inc. v. FAA) is published on Counsel Stack Legal Research, covering Court of Appeals for the First Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.
Bluebook
Echo, Inc. v. FAA, (1st Cir. 1995).
Opinion
USCA1 Opinion
UNITED STATES COURT OF APPEALS
FOR THE FIRST CIRCUIT
____________________
No. 94-1627
ECHO, INC.,
Petitioner,
v.
DAVID R. HINSON, ADMINISTRATOR, FEDERAL AVIATION ADMINISTRATION,
Respondent.
____________________
ON PETITION FOR REVIEW OF AN ORDER
OF THE NATIONAL TRANSPORTATION SAFETY BOARD
____________________
Before
Torruella, Chief Judge, ___________
Coffin, Senior Circuit Judge, ____________________
and Cyr, Circuit Judge. _____________
____________________
James G. Goggin with whom Carl E. Kandutsch was on brief for ________________ __________________
petitioner.
James W. Tegtmeier with whom Kathleen A. Yodice was on brief for __________________ ___________________
respondent.
____________________
February 9, 1995
____________________
COFFIN, Senior Circuit Judge. On the evening of November _____________________
19, 1993, an emergency medical evacuation helicopter operated by
petitioner Echo, Inc. (Echo) ran out of fuel, lost engine power,
and crashed into Casco Bay off the Maine coast, killing three
passengers. The Federal Aviation Administration (the FAA)
charged the pilot and Echo with violating several aviation safety
regulations and issued emergency orders revoking Echo's
certificate to operate as an air carrier, a sanction upheld by
the National Transportation Safety Board (the Board). Echo
petitions for review. We affirm.
I. Background __________
A. Facts _____
Echo is a Maine corporation established in 1985 by John G.
Rafter, Jr. to provide commercial flight services by helicopter
in the Portland area. Rafter is Echo's president, director of
operations, director of maintenance, and chief pilot. In 1993,
Rafter founded another company, Airmed Skycare, Inc. (Airmed),
which was devoted exclusively to emergency medical services.1
Airmed owned its own helicopter for air ambulance flights and
employed flight nurses and paramedics. It contracted with Echo
to supply the pilots for its flights. In the afternoon of
November 19, 1993, Airmed received a call requesting that a burn
victim be flown from Ellsworth, Maine to Portland for treatment.
With Rafter as pilot, and flying under Echo's certificate to
____________________
1 Rafter was also Airmed's president and majority
shareholder.
-2-
operate as an air carrier, the helicopter took off from Portland
to Ellsworth.
The weather conditions at the time of takeoff were, in the
words of Echo, "marginal," because of fog and light rain.
Nevertheless, Rafter concluded that the flight could be made
safely under Visual Flight Rules (VFR), and he took off. The
trip to Ellsworth was successful. The medical team picked up the
burn victim, and the helicopter began its return flight.
Approximately fifty miles northeast of Portland, however, weather
conditions deteriorated. The helicopter, then travelling at an
altitude of approximately 800 feet, entered the clouds; Rafter
was no longer able to navigate visually. He requested and
received Instrument Flight Rules (IFR) handling from air traffic
control at the Brunswick Naval Air Station, which instructed him
to climb above the clouds to 3,000 feet. Rafter climbed to a
higher altitude and proceeded to navigate by the helicopter's
instruments.
It is clear that, under normal conditions, neither Rafter
nor the helicopter was authorized to operate under IFR. The
operations specifications on Echo's air carrier certificate
authorized Echo to operate on "VFR only." Further, the
helicopter did not contain all the equipment required for IFR
operation. Finally, Rafter did not have the recent operational
experience necessary for IFR operation. Echo maintains that,
because of the emergency situation caused by weather conditions,
operation under IFR was justified pursuant to 14 C.F.R. 91.3(b)
-3-
("In an in-flight emergency requiring immediate action, the pilot
in command may deviate from any rule to the extent necessary to
meet that emergency."). Rafter did not declare an emergency,
however, or advise air traffic that he, Echo, and the helicopter
were all unauthorized to operate under IFR, conduct he later
ascribed to "pilot ego."
Not having been advised otherwise, the air traffic
controller treated the flight as normal IFR traffic. At
approximately 8:15 p.m., after tracking the flight for thirty
minutes, Brunswick Naval Air Station passed it off to Portland
Approach Control. Meanwhile, at the higher elevation, the
helicopter was encountering strong headwinds and turbulence,
causing slower progress to Portland than Rafter had anticipated.
Air traffic in Portland noticed that the helicopter was not
maintaining its assigned course or altitude, which Rafter later
attributed to the demands of piloting under IFR and in turbulence
when the helicopter was not properly equipped for IFR operation.
Six or seven minutes after contacting Portland Approach Control,
Rafter noticed that he was running low on fuel. He advised
Portland air traffic and requested a direct instrument approach
to runway 29. Air traffic gave him top priority, but it was too
late. Rafter soon reported a loss of fuel pressure, and the
engine lost power. About eight miles north of Portland, the
helicopter crashed into Casco Bay. The burn patient, paramedic
Free access — add to your briefcase to read the full text and ask questions with AI
Related
Robert K. Johnson v. National Transportation Safety Board
979 F.2d 618 (Seventh Circuit, 1992)
Thomas D. Hite v. National Transportation Safety Board
991 F.2d 17 (First Circuit, 1993)
Cite This Page — Counsel Stack
Bluebook (online)
Echo, Inc. v. FAA, Counsel Stack Legal Research, https://law.counselstack.com/opinion/echo-inc-v-faa-ca1-1995.