The U.S. aircraft register, updated daily
Accidents · NTSB WPR10FA120 · Final report

Piper PA-28-181 accident near Phoenix, Arizona, January 28, 2010

On January 28, 2010 at about 3:37 pm local time, a Piper PA-28-181, registered N293PA, was substantially damaged in an accident during maneuvering (low-alt flying) near Phoenix, Arizona (Phoenix Deer Valley Airport). It was an instructional flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The student pilot’s decision to take off in marginal visual flight rules conditions, which resulted in an encounter with low clouds, and the pilot's failure to maintain clearance from wires while maneuvering in the traffic pattern for landing.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 28, 2010 · about 3:37 pm local time
Place
Phoenix, Arizona · Phoenix Deer Valley Airport · map
Type
Accident
Injuries
1 person was killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA-28-181 · all PA-28-181s on the register
Registration
N293PA · registry record · serial 2843503
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

Shortly after takeoff for the student pilot’s second solo cross-country flight, she was advised by the air traffic controller to make a departure on the right downwind leg of the traffic pattern. While on the downwind leg, the pilot requested to return to the airport and make a full-stop landing. The controller instructed the pilot to continue the right-hand pattern and to follow the traffic in front of her. The controller then inquired if she needed assistance, to which she responded “because of ceiling.” The controller again advised her to follow the traffic in front of her, and she responded that she had it in sight. The controller then cleared her to land, which she acknowledged. The controller subsequently asked the pilot if she had the runway in sight, after which a short inaudible transmission was received. A review of the radar data indicated that the pilot was following a normal right-hand traffic pattern until the base leg, where she overflew the final approach for the runway. Witnesses in the area reported seeing the airplane flying very low before hearing a loud bang. The airplane impacted a low wire span about 30 feet above ground level and continued another 400 feet before hitting another set of wires and crashing into a field. The weather reported in the area at the time by witnesses and first responders was low clouds and fog. It is likely that the pilot either encountered the low clouds or was attempting to remain below the clouds when the collision with the wires occurred. Postaccident examination of the airplane and engine did not reveal evidence of a mechanical failure or malfunction that would have precluded normal operation. Visual flight rules (VFR) conditions existed over most of western Arizona; however, the accident site bordered the area between marginal VFR and VFR conditions. The weather observation at the time of the accident included a 1,000-foot broken cloud layer with 5 miles of visibility.

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

  1. VFR encounter with IMC during maneuvering (low-alt flying) defining event
  2. Controlled flight into terrain or object (CFIT) during approach (VFR pattern base)

The NTSB's findings

  • cause Environmental issues › Physical environment › Object/animal/substance › Wire › Response/compensation
  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Decision related to condition
  • cause Personnel issues › Action/decision › Info processing/decision › (general) › Student pilot

Dual student

  • Certificate: student
  • Flight time: 68 hours in all; 68 in this make and model; 68 in the last 90 days; 34 in the last 30 days; 7 as pilot in command
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 9,127 hours
  • Last inspection: annual inspection, January 20, 2010; 36 hours since
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360 SERIES (piston); 0 hours total
  • Operator: Transpac Aviation Academy

The flight

  • Departed from: DVT Phoenix AZ at 3:31 pm
  • Destination: E25 Wickenburg AZ

Weather at the time

  • Light: daylight
  • Wind: from 090° at 3 knots
  • Visibility: 8 statute miles
  • Sky: broken clouds at 1,900 ft; scat at 1,300 ft
  • Temperature: 52°F (11°C), dew point 48°F (9°C)
  • Altimeter: 29.92 inHg
  • Observation at 3:36 pm from DVT, 2 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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.