The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB LAX03FA066 · Final report

Cessna 182H and Grumman F6F-5 mid-air collision near Parker, Arizona, January 11, 2003

On January 11, 2003 at about 11:00 pm local time, 2 aircraft, Cessna 182H (N8567S) and Grumman F6F-5 (N4994V), were involved in a mid-air collision near Parker, Arizona (Avi Suquilla Airport). 2 people were killed; 1 other was unhurt. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

failure of both pilot's to see and avoid one another while maneuvering in the traffic pattern. A factor in the accident was the inability of the Cessna pilot to communicate on the CTAF frequency due to the limitations of his radios.
failure of both pilot's to see and avoid one another while maneuvering in the traffic pattern. A factor in the accident was the inability of the Cessna pilot to communicate on the CTAF frequency due to the limitations of his radios.

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

What the record shows

Date
January 11, 2003 · about 11:00 pm local time
Place
Parker, Arizona · Avi Suquilla Airport · map
Type
Accident · mid-air collision
Injuries
2 people were killed; 1 other was unhurt.
Weather
visual conditions (good weather)
Aircraft 1
Cessna 182H · all 182Hs on the register
Registration
N8567S · registry record · serial 18256667
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)
Aircraft 2
Grumman F6F-5 · all F6F-5s on the register
Registration
N4994V · registry record · serial 93879
Damage
Substantial damage
Flight
Air show or air race flight · general aviation rules (Part 91)

The NTSB's narrative for the Cessna 182H final · quoted from the NTSB record

A Cessna 182 and a Grumman F6F-5 collided in flight on the downwind leg of the airport traffic pattern for runway 19. The Cessna was departing on runway 19 with a left climbing turnout northbound, and the Grumman F6F-5 warbird was returning to land and had entered the airport traffic area from the north. The collision occurred about midfield on the left downwind leg for runway 19 when the Grumman overtook the climbing Cessna. The Grumman pilot was monitoring the Unicom frequency and reported several miles from the airport inbound for the overhead approach to runway 19. He overheard other aircraft in the pattern and decided to follow an F-86 warbird that was turning base to final for an overhead approach. He flew over the runway centerline about 600 feet above ground level. Near the departure end of the runway he looked left to see if there was any traffic on the downwind leg. No traffic was observed so he announced that he was in the left break for downwind and turned left to the downwind leg and climbed to the pattern altitude. At pattern altitude he was abeam the departure end of the runway. He located his reported traffic in the pattern; one was on final, one on base, and the F-86 was on his right on a wide downwind and ahead of him. He chose to follow the F-86. About midfield, while straight and level on the downwind leg, the pilot started the Before Landing Check List. During that procedure he checked his position relative to the runway. At that instant, another aircraft came into view from below and ahead of him and the collision occurred. He transmitted the collision information and subsequently landed with substantial damage to the left wing. The left wing of the Grumman impacted at the base of the rudder and vertical stabilizer of the Cessna, thus severing it from the airplane. The uncontrolled airport was sponsoring an Air Expo, which consisted of static and aerial formation flights, flybys, and parachuting events. The airport routinely provides an aeronautical advisory station (CTAF) on 122.725 MHz, and provides wind and preferred runway information. The CTAF operator at the airport did not recall hearing the Cessna on frequency. Visual examination of the Cessna's two damaged communication radios with only 25 kc frequency spacing revealed the top radio was selected to 122.7, and the other was 121.902 MHz. The Grumman airplane had one with 25 kc frequency spacing; however, the pilot was using a handheld VHF radio for transmissions on 75 kc spacing for the airport's CTAF frequency, 122.725.

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 NTSB's narrative for the Grumman F6F-5 final · quoted from the NTSB record

A Cessna 182 and a Grumman F6F-5 collided in flight on the downwind leg of the airport traffic pattern for runway 19. The Cessna was departing on runway 19 with a left climbing turnout northbound, and the Grumman F6F-5 warbird was returning to land and had entered the airport traffic area from the north. The collision occurred about midfield on the left downwind leg for runway 19 when the Grumman overtook the climbing Cessna. The Grumman pilot was monitoring the Unicom frequency and reported several miles from the airport inbound for the overhead approach to runway 19. He overheard other aircraft in the pattern and decided to follow an F-86 warbird that was turning base to final for an overhead approach. He flew over the runway centerline about 600 feet above ground level. Near the departure end of the runway he looked left to see if there was any traffic on the downwind leg. No traffic was observed so he announced that he was in the left break for downwind and turned left to the downwind leg and climbed to the pattern altitude. At pattern altitude he was abeam the departure end of the runway. He located his reported traffic in the pattern; one was on final, one on base, and the F-86 was on his right on a wide downwind and ahead of him. He chose to follow the F-86. About midfield, while straight and level on the downwind leg, the pilot started the Before Landing Check List. During that procedure he checked his position relative to the runway. At that instant, another aircraft came into view from below and ahead of him and the collision occurred. He transmitted the collision information and subsequently landed with substantial damage to the left wing. The left wing of the Grumman impacted at the base of the rudder and vertical stabilizer of the Cessna, thus severing it from the airplane. The uncontrolled airport was sponsoring an Air Expo, which consisted of static and aerial formation flights, flybys, and parachuting events. The airport routinely provides an aeronautical advisory station (CTAF) on 122.725 MHz, and provides wind and preferred runway information. The CTAF operator at the airport did not recall hearing the Cessna on frequency. Visual examination of the Cessna's two damaged communication radios with only 25 kc frequency spacing revealed the top radio was selected to 122.7, and the other was 121.902 MHz. The Grumman airplane had one with 25 kc frequency spacing; however, the pilot was using a handheld VHF radio for transmissions on 75 kc spacing for the airport's CTAF frequency, 122.725.

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 for the Cessna 182H from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 1,000 hours in all; 11 in the last 90 days
  • Last flight review: August 1, 2001
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 3,362 hours
  • Last inspection: annual inspection, July 1, 2002
  • Maximum gross weight: 2,800 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental O-470-L (piston); 0 hours total

The flight

  • Departed from: P20 Parker AZ at 10:55 pm
  • Destination: HII Lake Havasu AZ
  • Flight plan: none
  • Runway 19, 4,780 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 350° at 12 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 68°F (20°C), dew point 39°F (4°C)
  • Altimeter: 30.09 inHg
  • Observation at 10:56 pm from EED, 41 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

The factual record for the Grumman F6F-5 from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: airline transport pilot, flight instructor
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 12,700 hours in all; 35 in this make and model; 225 in the last 90 days; 75 in the last 30 days; 10,430 as pilot in command; 842 on instruments
  • Last flight review: November 1, 2002
  • Medical certificate: Class 1 (valid medical--w/ waivers/lim.)
  • Seat: sngl
  • Injury: no injuries

The aircraft

  • Airframe total time: 2,075 hours
  • Last inspection: condition inspection, March 2, 2002
  • Maximum gross weight: 12,480 lb
  • Seats: 1
  • Landing gear: retractable
  • Engine: Pratt & Whitney R-2800-79 (piston); 0 hours total

The flight

  • Departed from: P20 Parker at 10:30 pm
  • Destination: P20
  • Flight plan: none
  • Runway 19, 4,780 ft by 75 ft

Injuries

FatalSeriousMinorNone
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.

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number LAX03FA066.