ASN Wikibase Occurrence # 348885
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Saturday 16 December 2023 |
| Time: | 16:54 |
| Type: |  Cessna 172G Skyhawk |
| Owner/operator: | Private |
| Registration: | N3992L |
| MSN: | 17254161 |
| Year of manufacture: | 1966 |
| Fatalities: | Fatalities: 3 / Occupants: 3 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | near Independence State Airport (7S5), Independence, OR -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | McMinnville Municipal Airport, OR (KMMV) |
| Independence State Airport, OR (7S5) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Information verified through data from accident investigation authorities |
On December 16, 2023, about 1654 Pacific standard time, a Cessna 172G airplane, N3992L, was substantially damaged when it was involved in an accident near Independence, Oregon. The pilot and the two pilot-rated-passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
According to the owner of the airplane, he allowed the pilot to use the airplane to gain his private pilot’s certificate and to continue using the airplane to gain his instrument rating and commercial certificate.
According to the pilot’s flight instructor, the pilot explained to him that he and a pilot-rated passenger were going to fly to the McMinnville Municipal Airport (MMV), McMinnville, Oregon, to practice instrument approaches [in VFR conditions]. The pilot-rated-passenger had an instrument airplane rating and would act as a safety pilot.
Automatic dependent surveillance-broadcast (ADS-B) data recorded the airplane as it departed the Independence State Airport (7S5) Independence, Oregon about 1500, and flew directly to MMV. The airplane made an approach to runway 22, followed by maneuvering in an area about 12 miles southwest of the airport. The airplane then maneuvered to the northeast of the airport and conducted a second approach, to runway 22, to a full stop at 1608.
The flight instructor had been monitoring the progress of the flight on an internet ADS-B provider and grew concerned due to fog that had built up around 7S5. He called the pilot who was on the ground at MMV. During the conversation, the flight instructor advised the pilot not to return to 7S5 because of the low visibility of about 500 ft. The pilot explained that he would fly to 7S5, asses the conditions and decide to either land or divert to McNary Field Airport (SLE) Salem, Oregon, or possibly return to MMV. The pilot informed the flight instructor that he had picked up a second pilot-rated-passenger at MMV.
ADS-B data showed that the airplane departed MMV at 1638 and proceeded directly to 7S5. A recording of the common traffic advisory frequency (CTAF) for 7S5 revealed the pilot made a ten-mile and a five-mile position report that included an intention to land. About three minutes later the pilot reported entering the downwind leg for landing to runway 34. Shortly afterwards five clicks were recorded from the CTAF frequency, consistent with activating the pilot controlled lighting to medium intensity. About one minute later, the last call made by the pilot advised 7S5 traffic that “92L was final for [runway] 34.” The last moments of the ADS-B data recorded the airplane as it entered the 7S5 downwind leg, about traffic pattern altitude of 1,200 ft mean sea level. The airplane then entered a descending 180° left-hand turn. During the turn, the airplane overshot the runway centerline to the east, corrected but overshot the centerline to the west. The last ADS-B data point recorded the airplane about 1500 ft southwest of the accident site, which was about 670 ft west of the approach end of runaway 34.
The airplane came to rest inverted on the edge of an open field, adjacent to the airport property. A postaccident fire reduced the fuselage to ash. The wings and empennage were not consumed by the fire. The engine had separated from the airplane and was about 60 ft northwest of the main wreckage. The propeller remained attached to the engine with both propeller blades exhibiting chordwise bends aft, toward the engine. The first point of probable impact was a wooden power distribution line support pole, originally about 80 ft tall, and about 60 ft southeast of the wreckage. The pole had separated into three major sections. The main section, from the ground up to about 69 ft, remained installed in the ground and was affixed with multiple power distribution lines. The middle section, about 12 ft in length, fell onto the right wing. A white color transfer was observed on this section. The top 4 ft of the pole had fragmented and was strewn about the wreckage. The pole had a dual-lamp, red warning light affixed to its top. The warning light separated from the pole and was among the wreckage. At least one power distribution line had fractured and fell to the ground near the wreckage. A section of the power distribution line was in the fuselage section of the wreckage.
Examination of the airframe and engine revealed no mechanical malfunctions or failures that would have precluded normal operation.
The airplane was recovered to a secure facility.
Accident investigation:
 |
|
Sources:
https://www.kptv.com/2023/12/17/3-die-plane-crash-that-caused-brush-fire-power-outage-near-independence/
https://eu.statesmanjournal.com/story/news/local/2023/12/16/plane-crash-in-independence-causing-power-outage-brush-fire/71948789007/
https://www.kgw.com/article/news/local/plane-crash-fire-power-outages-independence/283-797ea528-7d20-4ce6-bcb3-81fc82c3ddba
NTSB
https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=3992L
https://www.flightaware.com/live/flight/N3992L/history/20231217/0038Z/KMMV/7S5
https://globe.adsbexchange.com/?icao=a4a6e1&lat=44.870&lon=-123.228&zoom=13.0&showTrace=2023-12-17
https://www.airport-data.com/images/aircraft/001/662/001662062.jpg (photo)
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 17-Dec-2023 04:23 | Geno | Added |
| 17-Dec-2023 07:40 | fr7391 | Updated [Total fatalities, Source] |
| 17-Dec-2023 07:48 | RobertMB | Updated [Time, Aircraft type, Registration, Cn, Operator, Total occupants, Location, Phase, Nature, Departure airport, Destination airport, Source, Damage, Narrative, Category] |
| 17-Dec-2023 07:49 | harro | Updated [Other fatalities, Source] |
| 17-Dec-2023 17:08 | johnwg | Updated [Time, Source, Narrative, Category] |
| 18-Dec-2023 00:02 | Captain Adam | Updated [Time, Source, Narrative] |
| 19-Dec-2023 07:37 | RobertMB | Updated [Time, Source, Narrative] |
| 29-Dec-2023 20:07 | Captain Adam | Updated [Time, Source, Narrative, Accident report] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation