FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02FA049 · Robinson R44

12 Dec 2001 · Waukesha, WI, United States

WW Helicopters Robinson R44 · Accident: in flight collision with object en route

From Lawrence J Timmerman Airport (MWC) to East Troy Municipal Airport (57C)

Report a problem

Event

NTSB case
CHI02FA049
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Robinson R44

Aircraft type
Robinson R44
Category
Helicopter
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N7007F
Onboard fatalities
Unknown
Route
From Lawrence J Timmerman Airport (MWC), Milwaukee, WITo East Troy Municipal Airport (57C), East Troy, WI
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire, static
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Altitude/clearance, not maintained
  • Pilot in command › Flight into adverse weather, continued

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The helicopter, while in cruise flight, was destroyed when it impacted a static powerline, a vehicle and terrain . The pilot asked local ATC to fly in controlled airspace and was told to remain outside due to present IFR conditions. Those weather conditions were 1 1/2 statute miles visibility, drizzle, and overcast skies at 400 feet. A witness stated that he "was driving and saw a red light over what seemed like the median a few 100 ft. in the air. The light rose almost straight upward maybe another 200 ft and then began corkscrewing downward." The helicopter is placarded, "THIS ROTOCRAFT APPROVED FOR DAY AND NIGHT VFR [visual flight rules] OPERATIONS." An on-scene investigation revealed no pre-impact anomalies. The fiberglass chin portion of the front right side of the cabin had a linear tear. The right side forward and aft cabin doors had a linear scratch across them. The helicopter color scheme was blue, white, and red. A power line contractor stated, "I inspected the helicopter crash site at I-43, on December 14, 2001. I inspected the static wire span, hands on, and found some plastic and fiberglass shavings. I also found three different color paints, mainly blue, very little yellow and a tiny bit of red. ... The locations of apparent contact points on the shield wire was an area 35 - 40 feet just North of mid-span." A power line employee calculated the wire was about "146' over the roadway." Robinson Safety Notice SN-26 stated, "NIGHT FLIGHT PLUS BAD WEATHER CAN BE DEADLY ... When it is dark, the pilot cannot see wires or the bottom of clouds, nor low hanging scud or fog." A Flight For Life Pilot stated that a request was received for "Aeromedical transport from an accident on [Highway] 164 and [Interstate] -43 by the Waukesha Co. Sheriff's Dept. I determined weather conditions were not acceptable so the flight request was denied."

Probable cause

The pilot's continued flight into adverse weather and not maintaining altitude/clearance from the static line during cruise flight. Factors were the static wire, the darkness of night, the low ceiling, and the vehicle.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02FA049
Event ID
20011219X02422
Case number
CHI02FA049
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2001-12-13.
  • API snapshot SHA-256: 2a9ed3ab9c3ea2e397a471855eba524ca5787ba9799417084e9042e8497cc060; retrieved 2026-09-20T20:15:50.747Z.