PDA

View Full Version : First U.S. Pilot Jailed For A Domestic Aircraft Accident


Larry Dighera
June 20th 08, 07:40 PM
Here's a timely story about piloting and the law. While I might
disagree with some of the FSDO Inspector's conclusions, there seems to
be little doubt that the pilot made a fatal mistake in failing to
realize the substantial and unreasonable risk of death or great bodily
harm flying low over the river created.. That said, you can bet the
DA wasn't offering a plea bargain because he believed a conviction was
assured.


http://www.aopa.org/members/files/pilot/2008/accident0807.html
July 2008 Volume 51 / Number 7
After the Accident
From ultimate freedom to incarceration

By Dave Hirschman

...
This year, Strub became the first U.S. pilot jailed for a domestic
aircraft accident. He pleaded guilty to reduced charges of
negligent operation of a motor vehicle and disorderly conduct and
was sentenced to 30 days in jail, 150 days home confinement,
fines, court costs, and two years probation during which he won’t
be allowed to fly. ...

FAR 91.119 places no limit on how low pilots are allowed to fly
over sparsely populated areas or open water, as long as they stay
at least 500 feet from any persons or vessels and can glide to a
landing in case of engine failure without “undue hazard to persons
or property on the surface.”

An FAA investigator later cited Strub for “careless and reckless”
flying, defining the river as a “congested area,” and said Strub
violated minimum safe altitude rules that require pilots to fly at
least 1,000 feet above or 2,000 feet horizontal distance from
obstacles. Strub said he believed at the time of the accident he
was flying over a portion of the river that was free of hazards.
...

Strub was charged with vehicular homicide, a felony that carries a
maximum sentence of 10 years in prison. ...

To convict, a jury would have to find Strub had acted “with intent
to cause damage,” or that injury or death “would probably result”
from his actions. Strub believed he could show that the crash was
purely accidental, and that he never would have flown low over the
river if he thought he was putting his passenger, his airplane, or
himself, in jeopardy. ...



Here's a link to copy of the Criminal Complaint filed against the
pilot (and excerpts thereof):

http://www.wisconsinrapidstribune.com/assets/pdf/U059422129.PDF
Criminal Complaint

Count 1: HOMICIDE BY NEGLIGENT OPERATION OF AN AIRPLANE
The above-named defendant on or about Saturday, August 28, 2004,
in the Village of Port Edwards, Wood County, Wisconsin, did cause
the death of Kimberly Reed by the negligent operation or handling
of an airplane, contrary to sec. 940.10(1), 939.50(3)(g) Wis.
Stats....

Strub states that while flying along the River at a low
altitude because he believed he could do so, he saw some power
lines across the River. He attempted to pull the plane up but was
unsuccessful and struck the lines causing the plane to crash into
the River. Strub stated that after freeing himself, he went to
Reed but could not free her because the top of the wing had
collapsed over her seat. ...

Ronald Miller, Senior Electrical Project Manager for Domtar
Papers, obtained measurements of the power poles and lines
involved in the crash. Miller advised that there would have been
three poles on the west and east sides of the River. On the west
side, the center pole had a total length of 71 feet above the
ground. The other poles would have had a total length of 56 feet
above the ground. On the east side of the River, the center pole
had a total length above ground of 54 feet and the two outer poles
would have had a total length of 39 feet above ground. Miller
further states that due to the sag factor of the lines over the
River, he believed that the sag or lower most part of the lines
over the River would have been approximately 48 feet. Miller also
indicated that when the crash occurred, the lines were never
severed from the impact, however, the poles on the east side of
the River were pulled down. ...


5. On October 28, 2004, Karen Krueger, Aviation Safety Inspector
(ASI) for the Federal Aviation Administration (FAA), reviewed her
findings with Inv. Gosh. It should be noted that ASI Krueger has
28½ years in her capacity as an Aviation Safety Inspector and that
her duties include pilot certification, surveillance
responsibility of small air carriers, investigations of accidents
and enforcement of FAA actions. Her findings revealed that
Strub was violating two regulations in the way he piloted his
plane. Her opinion was that he flew in violation of § 91.119 of
the US FAR 91.16, which is entitled “Minimum Safe Altitudes” that
requires an altitude of 500 feet about the surface over congested
areas. This would include that an aircraft should not be operated
closer than 500 feet between a person, vessel, vehicle or
structure. She further believes that his piloting was in violation
of FAR 91.13 entitled “Careless or Reckless Operation of an
Aircraft.” ASI Krueger’s opinion was that Strub was negligent in
the piloting of the airplane over the River flying at altitudes
somewhere in the area of 50 feet above the water. ASI Krueger
states that all pilots are required to fly at higher altitude so
that if there is a problem with the aircraft, the pilot can
attempt to safely land. The distances off the ground that Strub
was piloting his plane would clearly not allow him to recover from
any engine problem. ...



Here are links to National Transportation Safety Board investigatory
documents (and excerpts thereof):

http://www.ntsb.gov/ntsb/GenPDF.asp?id=CHI04LA243&rpt=fa
I noticed the power lines not more that 1/2 second before impact."
The main landing gear struck the power lines and the airplane
landed inverted in the river in about 3-4 feet of water.
The pilot reported that he had flown the river going south from
ISW "many times." He reported that he was not where he thought he
was when the accident occurred. He reported that he thought he was
4 miles south of his location.



http://www.ntsb.gov/ntsb/GenPDF.asp?id=CHI04LA243&rpt=fi
The National Transportation Safety Board determines the probable
cause(s) of this accident as follows.

The pilot's improper in-flight decision when he decided to fly at
a low altitude over the river and failed to maintain clearance
from the power lines. A factor was the wires.

Findings
1. (C) IN-FLIGHT PLANNING/DECISION - IMPROPER - PILOT IN COMMAND
2. (C) ALTITUDE - LOW - PILOT IN COMMAND
3. (C) ALTITUDE/CLEARANCE - NOT MAINTAINED - PILOT IN COMMAND
4. (F) OBJECT - WIRE,TRANSMISSION



http://www.ntsb.gov/ntsb/brief2.asp?ev_id=20040901X01341&ntsbno=CHI04LA243&akey=1


Here are links to the Wisconsin state criminal statutes with which the
pilot was charged:

http://www.legis.state.wi.us/statutes/Stat0940.pdf
CHAPTER 940
CRIMES AGAINST LIFE AND BODILY SECURITY
940.10 Homicide by negligent operation of vehicle.
(1) Whoever causes the death of another human being by the
negligent operation or handling of a vehicle is guilty of a Class
G felony.

History: 1987 a. 399; 1997 a. 295; 2001 a. 109.
Judicial Council Note, 1988 Homicide by negligent operation of
vehicle is analogous to prior s. 940.08. The mental element is
criminal negligence as defined in s. 939.25. [Bill 191-S]

A motorist was properly convicted under this section for running a
red light at 50 m.p.h., even though the speed limit was 55 m.p.h.
State v. Cooper, 117 Wis. 2d 30, 344 N.W.2d 194 (Ct. App. 1983).
The definition of criminal negligence as applied to homicide by
negligent operation of a vehicle is not unconstitutionally vague.
State v. Barman, 183 Wis. 2d 180, 515 N.W.2d 493 (Ct. App. 1994).
A corporation may be subject to criminal liability under this
section. State v. Knutson, Inc. 196 Wis. 2d 86, 537 N.W.2d 420
(Ct. App. 1995), 93-1898. See also State v. Steenberg Homes, Inc.
223 Wis. 2d 511, 589 N.W.2d 668 (Ct. App. 1998), 98-0104.
It is not a requirement for finding criminal negligence that the
actor be specifically warned that his or her conduct may result in
harm. State v. Johannes, 229 Wis. 2d 215, 598 N.W.2d 299 (Ct. App.
1999), 98-2239. The common law “year-and-a-day rule” that no
homicide is committed unless the victim dies within a year and a
day after the injury is inflicted is abrogated, with prospective
application only. State v. Picotte, 2003 WI 42, 261 Wis. 2d 249,
661 N.W.2d 381, 01-3063.



http://www.legis.state.wi.us/statutes/Stat0939.pdf
939.25 Criminal negligence. (1) In this section, “criminal
negligence” means ordinary negligence to a high degree, consisting
of conduct that the actor should realize creates a substantial
and unreasonable risk of death or great bodily harm to another,
except that for purposes of ss. 940.08 (2), 940.10 (2) and 940.24
(2), “criminal negligence” means ordinary negligence to a high
degree, consisting of conduct that the actor should realize
creates a substantial and unreasonable risk of death or great
bodily harm to an unborn child, to the woman who is pregnant with
that unborn child or to another.
(2) If criminal negligence is an element of a crime in chs. 939
to 951 or s. 346.62, the negligence is indicated by the term
“negligent” or “negligently”.
History: 1987 a. 399; 1989 a. 56 s. 259; 1997 a. 180, 295.
Judicial Council Note, 1988: This section is new. It provides a
uniform definition of criminal negligence, patterned on prior ss.
940.08 (2), 940.24 (2) and 941.01 (2).
Criminal negligence means the creation of a substantial and
unreasonable risk of death or great bodily harm to another, of
which the actor should be aware. [Bill 191-S]
The definition of criminal negligence as applied to homicide by
negligent operation of a vehicle is not unconstitutionally vague.
State v. Barman, 183 Wis. 2d 180, 515 N.W.2d 493 (Ct. App. 1994).



http://www.legis.state.wi.us/statutes/Stat0939.pdf
939.50 Classification of felonies. (
(1) Whoever causes the death of another human being by the
negligent operation or handling of a vehicle is guilty of a Class
G felony.


Below are links to case law discussions of the statutes:


http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=wi&vol=app2%5C98-0104&invol=1
Section 940.10, Stats.

Under Wisconsin's homicide by the negligent operation of a
vehicle statute, "[w]hoever causes the death of another human
being by the negligent operation or handling of a vehicle is
guilty of a Class E felony." Section 940.10, Stats. ...

Sufficiency of the Evidence.

Homicide by the negligent use of a vehicle has three
elements: (1) the defendant caused a death, (2) by criminal
negligence, (3) in the operation or handling of a vehicle.

Knutson , 196 Wis.2d at 109, 537 N.W.2d at 428. One cannot be held
criminally liable for ordinary negligence under §940.10, Stats.
Rather, the negligent act must rise to the level of criminal
negligence. Knutson , 196 Wis.2d at 109, 537 N.W.2d at 428.

Criminal negligence differs from ordinary negligence
in two respects. First, the risk is more serious-death or great
bodily harm as opposed to simple harm. Second, the risk must be
more than an unreasonable risk-it must also be substantial.
Criminal negligence involves the same degree of risk as criminal
recklessness-an unreasonable and substantial risk of death or
great bodily harm. The difference between the two is that
recklessness requires that the actor be subjectively aware of the
risk, while criminal negligence requires only that the actor
should have been aware of the risk-an objective standard.




http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=wi&vol=2007%5C31258&invol=2
Wis. Stat. ? 940.10(1) (2005-06).[1]? A person who ?causes the
death of an unborn child by the negligent operation or handling of
a vehicle? is guilty of homicide of an unborn child by negligent
operation of a vehicle.? Wis. Stat. ? 940.10(2).? The crime of
homicide by negligent operation of a vehicle contains three
essential elements: ?(1) the defendant operated a vehicle; (2) the
defendant operated the vehicle in a criminally negligent manner;
and (3) the defendant?s criminal negligence caused the death of
the victim.

June 20th 08, 08:38 PM
On Jun 20, 1:40*pm, "Darkwing" <theducksmail"AT"yahoo.com> wrote:
> "Larry Dighera" > wrote in message
>
> ...
>
>
>
>
>
> > Here's a timely story about piloting and the law. *While I might
> > disagree with some of the FSDO Inspector's conclusions, there seems to
> > be little doubt that the pilot made a fatal mistake in failing to
> > realize the substantial and unreasonable risk of death or great bodily
> > harm flying low over the river created.. *That said, you can bet the
> > DA wasn't offering a plea bargain because he believed a conviction was
> > assured.
>
> > * *http://www.aopa.org/members/files/pilot/2008/accident0807.html
> > * *July 2008 *Volume 51 / Number 7
> > * *After the Accident
> > * *From ultimate freedom to incarceration
>
> > * *By Dave Hirschman
>
> > * *...
> > * *This year, Strub became the first U.S. pilot jailed for a domestic
> > * *aircraft accident. He pleaded guilty to reduced charges of
> > * *negligent operation of a motor vehicle and disorderly conduct and
> > * *was sentenced to 30 days in jail, 150 days home confinement,
> > * *fines, court costs, and two years probation during which he won't
> > * *be allowed to fly. ...
>
> <snip>
>
> Sounds like an unfortunate accident caused by just flying to damn low.
> Unfortunately if you screw around it can bite you, whether you're flying an
> airplane or driving a car.- Hide quoted text -
>
> - Show quoted text -

From what I read of the accident, I'd say he was being irresponsible.
Taking someone on a sight seeing flight that low to the ground is not
safe. He got off fairly light considering he was responsible for
causing someone's death.

Darkwing
June 20th 08, 08:40 PM
"Larry Dighera" > wrote in message
...
> Here's a timely story about piloting and the law. While I might
> disagree with some of the FSDO Inspector's conclusions, there seems to
> be little doubt that the pilot made a fatal mistake in failing to
> realize the substantial and unreasonable risk of death or great bodily
> harm flying low over the river created.. That said, you can bet the
> DA wasn't offering a plea bargain because he believed a conviction was
> assured.
>
>
> http://www.aopa.org/members/files/pilot/2008/accident0807.html
> July 2008 Volume 51 / Number 7
> After the Accident
> From ultimate freedom to incarceration
>
> By Dave Hirschman
>
> ...
> This year, Strub became the first U.S. pilot jailed for a domestic
> aircraft accident. He pleaded guilty to reduced charges of
> negligent operation of a motor vehicle and disorderly conduct and
> was sentenced to 30 days in jail, 150 days home confinement,
> fines, court costs, and two years probation during which he won't
> be allowed to fly. ...

<snip>


Sounds like an unfortunate accident caused by just flying to damn low.
Unfortunately if you screw around it can bite you, whether you're flying an
airplane or driving a car.

Larry Dighera
June 20th 08, 10:37 PM
On Fri, 20 Jun 2008 12:38:21 -0700 (PDT), wrote in
>:

>Taking someone on a sight seeing flight that low to the ground is not
>safe.

Just out of curiosity, what do you consider unsafe about it?

Larry Dighera
June 20th 08, 11:39 PM
On Fri, 20 Jun 2008 15:40:14 -0400, "Darkwing"
<theducksmail"AT"yahoo.com> wrote in
>:

>
>Sounds like an unfortunate accident caused by just flying to damn low.

I wonder if those power lines are charted or NOTAMed.

Here's a chart centered on Alexander Field South Wood County (ISW):
http://skyvector.com/perl/code?id=KISW&scale=1

Here's a satellite image:
http://maps.google.com/maps?f=q&hl=en&geocode=&q=Port+Edwards,+wi&ie=UTF8&ll=44.356751,-89.852543&spn=0.104695,0.191231&t=h&z=13

Current NOTAMs:
https://pilotweb.nas.faa.gov/geo/icaoRadius.html?icao_id=KISW&radius=2

I don't find any mention of power lines across the river. How is a
pilot to know they are there?

Perhaps there is some culpability on the part of the owner of the
presumably unmarked power lines that cross the river:

Here's the Advisory Circular AC 70/7460-1K Obstruction Marking and
Lighting:
http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgAdvisoryCircular.nsf/0/b993dcdfc37fcdc486257251005c4e21/$FILE/AC70_7460_1K.pdf
a. Spherical Markers. Spherical markers are used
to identify overhead wires. Markers may be of
another shape, i.e., cylindrical, provided the projected
area of such markers will not be less than that
presented by a spherical marker.

1. Size and Color.
The diameter of the markers used on extensive
catenary wires across canyons, lakes, rivers, etc.,
should be not less than 36 inches (91cm). Smaller
20-inch (51cm) spheres are permitted on less
extensive power lines or on power lines below 50 feet
(15m) above the ground and within 1,500 feet (458m)
of an airport runway end. Each marker should be a
solid color such as aviation orange, white, or yellow.

2. Installations.
(a) Spacing. Markers should be spaced
equally along the wire at intervals of approximately
200 feet (61m) or a fraction thereof. Intervals
between markers should be less in critical areas near
runway ends (i.e., 30 to 50 feet (10m to 15m)). They
should be displayed on the highest wire or by another
means at the same height as the highest wire. Where
there is more than one wire at the highest point, the
markers may be installed alternately along each wire
if the distance between adjacent markers meets the
spacing standard. This method allows the weight and
wind loading factors to be distributed.

(b) Pattern. An alternating color scheme
provides the most conspicuity against...


>Unfortunately if you screw around it can bite you, whether you're flying an
>airplane or driving a car.
>

Operating an aircraft without adequate preflight planning is ALWAYS a
bad idea. In this case, it's not clear if there was adequate
information available to the pilot about the hazard of wires strung
across the river.

More_Flaps
June 21st 08, 03:30 AM
On Jun 21, 10:39*am, Larry Dighera > wrote:
> On Fri, 20 Jun 2008 15:40:14 -0400, "Darkwing"
> <theducksmail"AT"yahoo.com> wrote in
> >:
>
>
>
> >Sounds like an unfortunate accident caused by just flying to damn low.
>
> I wonder if those power lines are charted or NOTAMed.
>
> Here's a chart centered on Alexander Field South Wood County (ISW):http://skyvector.com/perl/code?id=KISW&scale=1
>
> Here's a satellite image:http://maps.google.com/maps?f=q&hl=en&geocode=&q=Port+Edwards,+wi&ie=...
>
> Current NOTAMs:https://pilotweb.nas.faa.gov/geo/icaoRadius.html?icao_id=KISW&radius=2
>
> I don't find any mention of power lines across the river. *How is a
> pilot to know they are there?
>
> Perhaps there is some culpability on the part of the owner of the
> presumably unmarked power lines that cross the river:
>
> Here's the Advisory Circular AC 70/7460-1K Obstruction Marking and
> Lighting:http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgAdvisoryC...
> * * a. Spherical Markers. Spherical markers are used
> * * to identify overhead wires. Markers may be of
> * * another shape, i.e., cylindrical, provided the projected
> * * area of such markers will not be less than that
> * * presented by a spherical marker.
>
> * * 1. Size and Color.
> * * The diameter of the markers used on extensive
> * * catenary wires across canyons, lakes, rivers, etc.,
> * * should be not less than 36 inches (91cm). Smaller
> * * 20-inch (51cm) spheres are permitted on less
> * * extensive power lines or on power lines below 50 feet
> * * (15m) above the ground and within 1,500 feet (458m)
> * * of an airport runway end. Each marker should be a
> * * solid color such as aviation orange, white, or yellow.
>
> * * 2. Installations.
> * * (a) Spacing. Markers should be spaced
> * * equally along the wire at intervals of approximately
> * * 200 feet (61m) or a fraction thereof. Intervals
> * * between markers should be less in critical areas near
> * * runway ends (i.e., 30 to 50 feet (10m to 15m)). They
> * * should be displayed on the highest wire or by another
> * * means at the same height as the highest wire. Where
> * * there is more than one wire at the highest point, the
> * * markers may be installed alternately along each wire
> * * if the distance between adjacent markers meets the
> * * spacing standard. This method allows the weight and
> * * wind loading factors to be distributed.
>
> * * (b) Pattern. An alternating color scheme
> * * provides the most conspicuity against...
>
> >Unfortunately if you screw around it can bite you, whether you're flying an
> >airplane or driving a car.
>
> Operating an aircraft without adequate preflight planning is ALWAYS a
> bad idea. *In this case, it's not clear if there was adequate
> information available to the pilot about the hazard of wires strung
> across the river. *

More_Flaps
June 21st 08, 03:33 AM
On Jun 21, 10:39*am, Larry Dighera > wrote:

> Operating an aircraft without adequate preflight planning is ALWAYS a
> bad idea. *In this case, it's not clear if there was adequate
> information available to the pilot about the hazard of wires strung
> across the river. *

He would not have hit them if he had not been low flying in an area
NOT approved for low flight. Since they are well below 500' and not
near an airfield they don't need markings or notams to avoid them,
just for the pilot obey the FARs

Cheers

June 21st 08, 04:41 AM
On Jun 20, 3:37*pm, Larry Dighera > wrote:
> On Fri, 20 Jun 2008 12:38:21 -0700 (PDT), wrote in
> >:
>
> >Taking someone on a sight seeing flight that low to the ground is not
> >safe.
>
> Just out of curiosity, what do you consider unsafe about it?

Oh, I don't know, power lines???

June 21st 08, 04:42 AM
On Jun 20, 3:37*pm, Larry Dighera > wrote:
> On Fri, 20 Jun 2008 12:38:21 -0700 (PDT), wrote in
> >:
>
> >Taking someone on a sight seeing flight that low to the ground is not
> >safe.
>
> Just out of curiosity, what do you consider unsafe about it?

Trees?

Engine failure at 20 feet?

Bird strike at low altitude?

Mxsmanic
June 21st 08, 10:45 AM
Larry Dighera writes:

> Just out of curiosity, what do you consider unsafe about it?

A flight that low should be considered unsafe by default, unless the entire
route has been recently scouted in advance (and in person, not by consulting
charts) to verify that no obstacles exist anywhere near the planned altitude
above ground of the flight. There will be no time or space to deal with such
obstacles during the flight itself.

Larry Dighera
June 21st 08, 04:30 PM
On Sat, 21 Jun 2008 07:51:03 -0400, John Smith > wrote
in >:
>
>The problem is that the FAA has deliberately refused to define
>"congested" so as to apply the term at their descretion in legal
>matters. This case seems to be an example of that.

From the chart and satellite image at the links below, how would you,
or any other reader, class the area where this mishap occurred,
uncontested? Congested?

Here's a chart centered on Alexander Field South Wood County (ISW):
http://skyvector.com/perl/code?id=KISW&scale=1

Here's a satellite image:
http://maps.google.com/maps?f=q&hl=en&geocode=&q=Port+Edwards,+wi&ie=UTF8&ll=44.356751,-89.852543&spn=0.104695,0.191231&t=h&z=13


It's unclear to me on exactly which part of the river this mishap
occurred, but personally, I would class the areas north, east, and
southwest of the field as congested. Obviously the green wetlands to
the south and west of the field are only congested with vegetation.

Mxsmanic
June 21st 08, 06:01 PM
John Smith writes:

> The problem is that the FAA has deliberately refused to define
> "congested" so as to apply the term at their descretion in legal
> matters. This case seems to be an example of that.

Since the pilot hit power lines and killed someone in the process in this
case, I'd tend to agree with the FAA here.

Buster Hymen
June 21st 08, 10:25 PM
Mxsmanic > wrote in
:

> John Smith writes:
>
>> The problem is that the FAA has deliberately refused to define
>> "congested" so as to apply the term at their descretion in legal
>> matters. This case seems to be an example of that.
>
> Since the pilot hit power lines and killed someone in the process in this
> case, I'd tend to agree with the FAA here.
>

You are a total asshole when it comes to aviation Anthony.

Gig 601Xl Builder
June 23rd 08, 06:13 PM
Larry Dighera wrote:
> On Fri, 20 Jun 2008 15:40:14 -0400, "Darkwing"
> <theducksmail"AT"yahoo.com> wrote in
> >:
>
>> Sounds like an unfortunate accident caused by just flying to damn low.
>
> I wonder if those power lines are charted or NOTAMed.
>
> Here's a chart centered on Alexander Field South Wood County (ISW):
> http://skyvector.com/perl/code?id=KISW&scale=1
>
> Here's a satellite image:
> http://maps.google.com/maps?f=q&hl=en&geocode=&q=Port+Edwards,+wi&ie=UTF8&ll=44.356751,-89.852543&spn=0.104695,0.191231&t=h&z=13
>
> Current NOTAMs:
> https://pilotweb.nas.faa.gov/geo/icaoRadius.html?icao_id=KISW&radius=2
>
> I don't find any mention of power lines across the river. How is a
> pilot to know they are there?
>
> Perhaps there is some culpability on the part of the owner of the
> presumably unmarked power lines that cross the river:


The key word in the AC below is in a.1. "extensive." Is one set of wires
considered extensive?

>
> Here's the Advisory Circular AC 70/7460-1K Obstruction Marking and
> Lighting:
> http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgAdvisoryCircular.nsf/0/b993dcdfc37fcdc486257251005c4e21/$FILE/AC70_7460_1K.pdf
> a. Spherical Markers. Spherical markers are used
> to identify overhead wires. Markers may be of
> another shape, i.e., cylindrical, provided the projected
> area of such markers will not be less than that
> presented by a spherical marker.
>
> 1. Size and Color.
> The diameter of the markers used on extensive
> catenary wires across canyons, lakes, rivers, etc.,
> should be not less than 36 inches (91cm). Smaller
> 20-inch (51cm) spheres are permitted on less
> extensive power lines or on power lines below 50 feet
> (15m) above the ground and within 1,500 feet (458m)
> of an airport runway end. Each marker should be a
> solid color such as aviation orange, white, or yellow.
>
> 2. Installations.
> (a) Spacing. Markers should be spaced
> equally along the wire at intervals of approximately
> 200 feet (61m) or a fraction thereof. Intervals
> between markers should be less in critical areas near
> runway ends (i.e., 30 to 50 feet (10m to 15m)). They
> should be displayed on the highest wire or by another
> means at the same height as the highest wire. Where
> there is more than one wire at the highest point, the
> markers may be installed alternately along each wire
> if the distance between adjacent markers meets the
> spacing standard. This method allows the weight and
> wind loading factors to be distributed.
>
> (b) Pattern. An alternating color scheme
> provides the most conspicuity against...
>

>
> Operating an aircraft without adequate preflight planning is ALWAYS a
> bad idea. In this case, it's not clear if there was adequate
> information available to the pilot about the hazard of wires strung
> across the river.

Then he should not have been site seeing with a passenger there until he
knew what was there.

When I got my helicopter rating I was taught to assume wires were every
where.

es330td
June 23rd 08, 07:30 PM
On Jun 20, 3:40*pm, "Darkwing" <theducksmail"AT"yahoo.com> wrote:
>
> Sounds like an unfortunate accident caused by just flying to damn low.
> Unfortunately if you screw around it can bite you, whether you're flying an
> airplane or driving a car.- Hide quoted text -
>
> - Show quoted text -

When I started flying, my CFI said that safe flight is found by
staying away from the edges: don't go too high or too low, don't go
too fast or too slow, keep the CG in the middle, stay away from the
clouds and don't ever take off too heavy. There is no mission
important enough to risk your and your passengers' lives to complete.
If you want to push the edges learn aerobatic flight but for the
normal GA pilot "Moderation in all things" is the key.

Rich Ahrens[_2_]
June 23rd 08, 10:16 PM
on 6/21/2008 4:25 PM Buster Hymen said the following:
> Mxsmanic > wrote in
> :
>
>> John Smith writes:
>>
>>> The problem is that the FAA has deliberately refused to define
>>> "congested" so as to apply the term at their descretion in legal
>>> matters. This case seems to be an example of that.
>> Since the pilot hit power lines and killed someone in the process in this
>> case, I'd tend to agree with the FAA here.
>>
>
> You are a total asshole when it comes to aviation Anthony.

Give him more credit than that - he's a total asshole at everything.

Larry Dighera
June 24th 08, 01:42 AM
On Mon, 23 Jun 2008 12:13:34 -0500, Gig 601Xl Builder
> wrote in
>:

>When I got my helicopter rating I was taught to assume wires were every
>where.

Exactly.

Google