ASN Wikibase Occurrence # 157815
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 27 July 2013 |
| Time: | 14:40 |
| Type: |  Piper PA-28R-200 Arrow II |
| Owner/operator: | Private |
| Registration: | N1549X |
| MSN: | 28R-7535322 |
| Year of manufacture: | 1975 |
| Total airframe hrs: | 7961 hours |
| Engine model: | Lycoming I0360 SER |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Lake Michigan north of Cudahy, WI -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Racine, WI (KRAC) |
| Oshkosh, WI (KOSH) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot was receiving flight-following services from an approach controller, who gave the pilot vectors to fly east over Lake Michigan and then north to avoid conflicting traffic. On the northerly heading, the accident pilot flew 1.4 miles behind the other airplane. When the accident pilot had the traffic in sight, the approach controller allowed him to pass behind the other airplane and then turn northbound as requested. Shortly thereafter, the approach controller lost radar contact with the pilot. Search and rescue operations were conducted, and the airplane was located in the lake. According to recorded radar data, the accident airplane’s flightpath crossed the other airplane’s flightpath at 1,800 feet mean sea level (msl) about 39 seconds after the other airplane passed the same location at the same altitude. Because the approach controller’s plan explicitly had the accident pilot pass behind the other airplane and the other airplane was descending from above the accident airplane, it is likely that the accident airplane encountered wake turbulence. Primary radar returns detected by airport surveillance radar were consistent with the in-flight breakup of the airplane. The approach controller did not issue a wake turbulence advisory to the pilot. Although wake turbulence is primarily the pilot’s responsibility, the Federal Aviation Administration Air Traffic Control Handbook does require controllers to provide pilots with a wake turbulence advisory if, in the controller’s opinion, wake turbulence may adversely affect their aircraft. In this case, the approach controller should have been cognizant of the potential hazard and issued a wake turbulence advisory to the pilot.
Probable Cause: An encounter with wake turbulence, which resulted in the pilot’s loss of control of the airplane and its subsequent in-flight breakup. Contributing to the accident was the approach controller’s failure to issue a wake turbulence advisory to the pilot.
Accident investigation:
 |
|
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 28-Jul-2013 01:26 | Geno | Added |
| 28-Jul-2013 04:11 | Geno | Updated [Aircraft type, Registration, Cn, Operator, Source, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 29-Nov-2017 08:49 | ASN Update Bot | Updated [Operator, Departure airport, Destination airport, Source, Narrative] |
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