LAX08FA265 · Cessna R172K
Franklin Aviation Cessna R172K and Cirrus Design Corp. SR22 · Accident: midair collision while maneuvering
Event
- NTSB case
- LAX08FA265
- 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
- 3 · 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 R172K
- Aircraft type
- Cessna 172
- 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
- N758NH
- Operator
- Franklin Aviation
- Onboard fatalities
- Unknown
- Route
- From Southwest Wyoming Regional Airport (RKS), Rock Springs, WYTo Southwest Wyoming Regional Airport (RKS), Rock Springs, WY
- 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
- Maneuvering
- 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
- 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 · Cirrus Design Corp. SR22
- Aircraft type
- Cirrus SR22
- 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
- N8341
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Polson Airport (8S1), Polson, MTTo Southwest Wyoming Regional Airport (RKS), Rock Springs, WY
- 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 · descent
- 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
- 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
Cause areas
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The Cessna was on a local solo instructional flight while the Cirrus was on an instrument-flight-rules flight plan and clearance to the airport. The Cessna was maneuvering northwest of the airport, and the Cirrus was descending toward the airport from the northwest. The air traffic controller working the flight cleared the Cirrus for a visual approach and advised the pilot to switch to the common traffic advisory frequency. About 2 minutes and 30 seconds before the collision, the controller advised the Cirrus of an aircraft (the Cessna) at his one o'clock position and 10 miles at 9500 feet mean sea level (msl). The Cirrus pilot responded, "thank you," and there was no further contact with the Cirrus. Radar data indicates that for the next 2 minutes, the Cessna maintained a northeasterly heading and climbed to 9,800 feet msl. About 30 seconds before the collision, the Cessna turned approximately 20 to 30 degrees right and continued on that heading, level at 9,800 feet msl. During this same 2 minute and 30 second period, the Cirrus was descending on a heading of about 130 degrees magnetic. The data depict the two airplanes converging perpendicular to one another and colliding about 5 nautical miles northwest of the airport at an altitude of about 9,800 feet msl, or 3,300 feet above the ground. The wreckage of the two airplanes was intermingled and scattered over an area of about 1,400 feet by 1,500 feet. During examination of the wreckage, transfer marks were identified consistent with the radar-derived collision angle. The Cirrus was equipped with a TCAS-like traffic advisory system that would alert the pilot of transponder equipped aircraft that pose a collision threat within a 0.55-mile radius. Based on the radar data, the system, if turned on, should have generated both an oral and visual traffic advisory starting about 30 seconds before and continuing until impact. It could not be determined whether the unit generated an advisory. It is possible that the geometry between the the system's antenna on top of the Cirrus and the transponder antenna on the bottom of the Cessna prevented the system from generating an advisory, but this could not be confirmed. Both airplanes were operating under visual conditions when they collided.
Probable cause
The failure of both pilots to see and avoid each other's aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08FA265
- Event ID
- 20080826X01316
- Case number
- LAX08FA265
- 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, 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: ef5e2af6a7fc95dea7d247e57dc63281184630badf4d43f3dc4f6127d575bafb; retrieved 2026-09-13T18:03:51.357Z.