LAX03FA066 · Cessna 182H
Cessna 182H and Grumman F6F-5 · Accident: midair collision en route
Event
- NTSB case
- LAX03FA066
- 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
- 2 · 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
Aircraft 1 · Cessna 182H
- Aircraft type
- Cessna 182
- 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
- N8567S
- Operator
- Robert L. Hatch · private individual
- Onboard fatalities
- Unknown
- Route
- From Avi Suquilla Airport (P20), Parker, AZTo Lake Havasu City Airport (HII), Lake Havasu, AZ
- 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
- En route · climb to cruise
- First occurrenceThe 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Aircraft 2 · Grumman F6F-5
- Aircraft type
- Grumman F6
- 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
- N4994V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From P20 · ParkerTo P20
- 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
- Approach · VFR pattern downwind
- First occurrenceThe 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
- Midair collision
- 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
- Pilot in command › Visual lookout, inadequate
- Pilot of other aircraft › Visual lookout, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03FA066
- Event ID
- 20030115X00072
- Case number
- LAX03FA066
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 013aa92d8cdc5bf89628d752449a85e720f207fc1583ae03e461beb3d0ba7355; retrieved 2026-09-20T19:31:39.314Z.