FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA323 · Republic RC-3

1 Jul 2009 · Burley, ID, United States

Republic RC-3 · Accident: collision during takeoff/landing during initial climb

From Burley, ID to Caldwell Executive Airport (EUL)

Report a problem

Event

NTSB case
WPR09LA323
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
0 · 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

Republic RC-3

Aircraft type
Republic RC-3
Category
Airplane
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
N87487
Operator
Ken Paulsen
Onboard fatalities
Unknown
Route
From Burley, IDTo Caldwell Executive Airport (EUL), Caldwell, ID
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
Initial climb
Defining eventThe 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
Collision during takeoff/landing
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
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The student pilot reported that despite his request for the airplane to be refueled with 30 gallons of fuel prior to takeoff, the fixed base operator had filled the airplane with 67.7 gallons of fuel. The flight instructor reported that after the student pilot was notified that the airplane had been topped off with fuel, he "ran the numbers in [his] head and determined it would be fine because of the same conditions that were present" for takeoff from a different airport earlier in the day. The student pilot reported that while on the initial climb from the airport, the airplane stopped climbing and began to descend. At an altitude of 100 feet above ground level, the flight instructor took control of the airplane to ensure a proper climbout speed was maintained. The airplane continued to descend and collided with power lines. Subsequently, the airplane nosed over and impacted the ground in a vacant lot. A witness reported that the airplane slowly accelerated down the 4,067-foot-long runway and used approximately 85 to 90 percent of the available runway to become airborne. The witness observed the airplane "climbing at an extremely slow rate," and stated it appeared that "the pilot attempted to increase the rate of climb twice," which resulted in the airplane’s "left wing starting to dip as it appeared to be approaching a stall." Examination of the airplane by a Federal Aviation Administration inspector revealed that the empennage had separated from the fuselage just aft of the cabin and that the rudder, vertical stabilizer, nose, and wings were structurally damaged. No mechanical anomalies were noted with the engine or airframe. Takeoff performance calculations for the reported weather conditions revealed that the airplane’s required takeoff distance to clear a 50-foot obstacle was 3,921 feet on a paved surface.

Probable cause

The flight instructor's failure to maintain clearance from power lines during takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA323
Event ID
20090702X01258
Case number
WPR09LA323
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: fdef3835b23766fd55f474f6a754ac98c8b630972d5c724c7ac4705f7bf4ea69; retrieved 2026-09-15T11:39:38.973Z.