Cessna 172H accident near Isle, Minnesota, July 18, 2003
On July 18, 2003 at about 3:10 pm local time, a Cessna 172H, registered N1606F, was destroyed in an accident near Isle, Minnesota (Isle Private Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed and 3 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain adequate airspeed which resulted in a stall. The trees, high density altitude, and the soft field were additional factors.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 18, 2003 · about 3:10 pm local time
- Place
- Isle, Minnesota · Isle Private Airport · map
- Type
- Accident
- Injuries
- 1 person was killed and 3 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172H · all 172Hs on the register
- Registration
- N1606F · registry record · serial 55001
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane was substantially damaged when it impacted trees and terrain during initial climb from a grass airstrip. The pilot attempted to depart with full fuel and three passengers on a local flight. A passenger aboard the airplane stated that the airplane banked to the right and then descended into the trees during the climb. Visual meteorological conditions prevailed at the time of the accident with an approximate density altitude of 2,339 feet mean sea level and 50 percent humidity. Damage to the airplane was consistent with a nose-down, low-speed impact. Examination of the wreckage revealed no anomalies with the flight control system and engine. The airplane was not equipped with shoulder harnesses, and the seat belts possessed stitching, which was not consistent with a manufactured product. The right rear passenger seat belt stitching separated at the lower attach point.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 264 hours in all; 183 in this make and model; 13 in the last 90 days; 7 in the last 30 days; 212 as pilot in command
- Last flight review: February 20, 2003
- Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 5,397.2 hours
- Last inspection: annual inspection, July 18, 2003; 6.2 hours since
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental O-300-D (piston); 0 hours total
The flight
- Departed from: MY72 Isle MN at 3:10 pm
- Destination: MY72
- Flight plan: none
- Runway 16, 2,460 ft by 160 ft
Weather at the time
- Light: daylight
- Wind: from 170° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 55°F (13°C)
- Altimeter: 30.20 inHg
- Observation at 2:56 pm from JMR, 18 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.