FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04FA197 · Robinson R22 Alpha

28 Jul 2004 · Mount Clemens, MI, United States

Robinson R22 Alpha · Accident: loss of control in flight on approach

From Oakland County International Airport (PTK) to Selfridge Air National Guard Base Airport (MTC)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CHI04FA197
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
Visual Meteorological Cond

Robinson R22 Alpha

Aircraft type
Robinson R22
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
N103MH
Operator
Michael J. Morton · private individual
Onboard fatalities
Unknown
Route Possible conflict
From Oakland County International Airport (PTK), Pontiac, MITo Selfridge Air National Guard Base Airport (MTC), Mount Clemens, MI
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
Approach
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
Loss of control in flight
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

  • Reason for occurrence undetermined

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 impacted terrain while attempting to land at a National Guard Base following a reported vibration in the helicopter. The pilot contacted air traffic control (ATC) stating he was 9 miles south of the base and requesting a clearance to transition through their airspace. The pilot was cleared through the airspace. When the helicopter was about 1 mile south of the base, the pilot reported to ATC that he was "... picking up a vibration." The controller asked the pilot to repeat the transmission and the pilot stated, "Yes sir the helicopter is starting to shake more violently sir." The controller informed the pilot that he could land at the base if he declared an emergency. Approximately 3 1/2 minutes later when the helicopter was 2 miles north of the base at 1,800 feet mean sea level (msl), the pilot reported that he was coming back to land. ATC cleared the pilot to land requesting if at all possible that the pilot land on the south side of the airport. The air traffic controllers viewed the helicopter through binoculars. They reported that they did not notice anything unusual with the helicopter and it appeared normal. One controller stated the helicopter crossed the northern end of the airport at 1,600 feet msl [1,020 above ground level (agl)]. Witnesses reported hearing the engine as the helicopter approached the airport. They stated that once the helicopter was approaching the south side of the airport, the nose pitched up then down. Witnesses described the descent angle as being between 45 and 70 degrees nose down. One controller estimated the descent began at an altitude of 1,400 to 1,500 feet msl [820 to 920 feet agl]. The helicopter impacted the grass leaving a wreckage trail approximately 299 feet long. Examination of the airframe, flight control systems, and engine did not reveal any failure/malfunction which would have resulted in the accident. A sound spectrum examination was performed on a re-recording of the ATC communications to document engine, rotor, or vibration sounds on the tape. This examination revealed that the rotor system background sounds were consistent with the main rotor rating at about 101% rpm. These sounds were consistent throughout the recording including the transmissions after the pilot reported a vibration. In addition, the tape was examined to determine if any airframe or rotor system vibrations could be identified. There were no additional sounds or vibrations identified during any of the transmissions.

Probable cause

A loss of control in flight for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04FA197
Event ID
20040801X01120
Case number
CHI04FA197
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: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 378070f62dd722641dbe09afb58c9ab6ab72fcd49887be367cd2cc81526003d8; retrieved 2026-09-20T18:24:09.512Z.