Cessna 172S accident near Park Rapids, Minnesota, September 13, 2009
On September 13, 2009 at about 3:30 am local time, a Cessna 172S, registered N523ND, was substantially damaged in an accident during takeoff near Park Rapids, Minnesota (Park Rapids Municipal airport). It was an instructional flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain a proper climb rate during a night takeoff.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 13, 2009 · about 3:30 am local time · cases in 2009
- Place
- Park Rapids, Minnesota · Park Rapids Municipal · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172S · all 172Ss on the register
- Registration
- N523ND · registry record · serial 172S10816
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot performed a go-around on the first attempted landing at the airport during night visual meteorological conditions. On the second attempt, he landed about mid-field and performed a stop and go landing. He initiated the takeoff using 10-degrees of flaps. The pilot reported that when he reached about 100 feet above ground level, he retracted the flaps. He felt that the airspeed was a little low (70 knots IAS) so he pushed the nose over. He stated that he did not think he was in a descent, but the airplane hit the ground about 100 feet from the end of the runway. The nose gear collapsed and both wings were damaged as the airplane bounced and skidded to a stop. The examination of the accident site revealed eight ground scars in the grass which were consistent with propeller strikes. The propeller blades exhibited leading edge nicks and gouges, chordwise scratching, and blade twist. The inspection of the airplane’s flight controls revealed no preexisting anomalies. The pilot reported that he had 112 hours of flight time with 112 hours in make and model. He had flown 9 hours at night which included 2 hours of night experience when he was pilot-in-command.
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
What happened, in order
- Abnormal runway contact during takeoff defining event
- Landing gear collapse during post (impact)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Climb rate › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Effect on operation
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 112 hours in all; 112 in this make and model; 44 in the last 90 days; 13 in the last 30 days; 19 as pilot in command
- Last flight review: July 27, 2009
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 1,020 hours
- Last inspection: approved inspection programme, September 9, 2009
- Maximum gross weight: 2,550 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-360-L2A (piston); 0 hours total
- Operator: University of North Dakota
The flight
- Departed from: PKD Park Rapids MN at 1:15 am
- Destination: GFK Grand Forks ND
- Flight plan: not recorded
- Runway 31, 5,498 ft by 100 ft
Weather at the time
- Light: night
- Wind: from 230° at 7 knots
- Visibility: 10 statute miles
- Sky: overcast at 7,000 ft
- Temperature: 64°F (18°C), dew point 61°F (16°C)
- Altimeter: 30.17 inHg
- Observation at 2:53 am from PKD, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on January 8, 2010. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 12 pages | View Download |
| 2 | Airbag Factual Report | PDF, 5 pages | View Download |
| 3 | Photo 1. View of Ground Scars | PDF, 1 page | View Download |
| 4 | Photo 2. Propeller | PDF, 1 page | View Download |
| 5 | Photo 3. View of Accident Site | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N523ND on the register today · the tail number may have moved to another aircraft since
- Cessna 172 Skyhawk 20,691 registered today · the model family and its accident history
- Cessna 72,673 aircraft on the register
- Engine: Lycoming IO-360-L2A 2,663 aircraft carry this series today · as the NTSB recorded it
- Park Rapids Muni/Konshok Field · nearest airport
- Grand Forks International · bound for
- Accidents and incidents in Minnesota 1,544 since 1982 · 209 in the last ten years
- Minnesota 6,969 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN09LA579.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
