37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 863748 |
Time | |
Date | 200912 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PVU.Airport |
State Reference | UT |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | DA42 Twin Star |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Flight Phase | Final Approach |
Person 1 | |
Function | Instructor |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 77.5 Flight Crew Total 1250 Flight Crew Type 234.1 |
Person 2 | |
Function | Trainee |
Qualification | Flight Crew Instrument Flight Crew Private |
Experience | Flight Crew Last 90 Days 30 Flight Crew Total 200 |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 0 Vertical 50 |
Narrative:
My student and I were flying a practice VFR approach into provo ut. We made contact with salt lake approach when we were about six miles east of the fairfield VOR. We were given no radar or separation service and were allowed to vector ourselves on to the final approach course. We intercepted the localizer and maintained 8000 ft until intercepting the glide slope; then we flew the glide slope. During the time with salt lake approach we became aware of another aircraft ahead of us on an approach into provo; and I started scanning for him. Salt lake approach told us to contact provo tower when we were on the localizer over lehi. Upon switching to provo tower's frequency we heard a cessna talking about being 10 out for a straight in. We then made contact with provo tower and were told we would be behind aircraft X; also that a cessna reported 10 miles to the north. I then started looking for both the cessna and aircraft X. Just before reaching wavit the cessna appeared about fifty feet below our aircraft. I took the controls; added power and started a climb as we passed over him. We tried to report what had happened but the cessna started reporting he was doing a 360 for spacing. After over flying him we maintained altitude and continued to fly towards the runway with my student watching him. I feel that part the problem was the cessna pilot's lack familiarity with operations for the provo area. He was not talking to salt lake approach prior to making a straight in approach. Blind spots were also to blame. He was below us and we were a low wing and we were above him and he was a high wing. Also lack of radar help contributed to this occurrence. Had radar been in place both of the aircraft could have known where the other was. This would also give air traffic control a better idea were all the aircraft were.
Original NASA ASRS Text
Title: A DA42 experienced a NMAC with a C-172 while shooting a practice approach to PVU.
Narrative: My student and I were flying a practice VFR approach into Provo UT. We made contact with Salt Lake Approach when we were about six miles east of the Fairfield VOR. We were given no radar or separation service and were allowed to vector ourselves on to the final approach course. We intercepted the localizer and maintained 8000 FT until intercepting the glide slope; then we flew the glide slope. During the time with Salt Lake Approach we became aware of another aircraft ahead of us on an approach into Provo; and I started scanning for him. Salt Lake approach told us to contact Provo Tower when we were on the localizer over LEHI. Upon switching to Provo Tower's frequency we heard a Cessna talking about being 10 out for a straight in. We then made contact with Provo Tower and were told we would be behind Aircraft X; also that a Cessna reported 10 miles to the North. I then started looking for both the Cessna and Aircraft X. Just before reaching WAVIT the Cessna appeared about fifty feet below our aircraft. I took the controls; added power and started a climb as we passed over him. We tried to report what had happened but the Cessna started reporting he was doing a 360 for spacing. After over flying him we maintained altitude and continued to fly towards the runway with my student watching him. I feel that part the problem was the Cessna pilot's lack familiarity with operations for the Provo area. He was not talking to Salt Lake Approach prior to making a straight in approach. Blind spots were also to blame. He was below us and we were a low wing and we were above him and he was a high wing. Also lack of radar help contributed to this occurrence. Had radar been in place both of the aircraft could have known where the other was. This would also give Air Traffic Control a better idea were all the aircraft were.
Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.