37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 369390 |
Time | |
Date | 199705 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : dpa |
State Reference | IL |
Altitude | msl bound lower : 2200 msl bound upper : 2200 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : dpa tracon : pit |
Operator | general aviation : instructional |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise other |
Flight Plan | None |
Person 1 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : commercial |
Experience | flight time last 90 days : 30 flight time total : 530 flight time type : 530 |
ASRS Report | 369390 |
Person 2 | |
Affiliation | government : faa |
Function | other personnel other |
Qualification | pilot : cfi pilot : instrument |
Events | |
Anomaly | other anomaly other |
Independent Detector | other other : unspecified |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | other |
Narrative:
In the process of completing cfii check ride -- examiner flying under hood, I am teaching partial panel skills. Examiner asks to be vectored for a VOR runway 10 approach dpa. I give vectors, call dupage tower to report, and report 5 mi southwest inbound. First, our position was 10 mi southwest. Next, I should have told dupage tower we were tracking the VOR course inbound, but did not. There was no traffic inbound, tower advised to call 2 mi out, verified our position southwest of VOR. I called 2 mi out and we leveled at 1500 ft and completed normal landing without difficulty. I should have advised dpa tower we were tracking the VOR radial inbound on initial call, but they did not ask, only verified we were southwest which I did. I also gave them the wrong mileage report on initial call. While not strictly wrong to track the VOR to airport on good VOR day, I should not have tracked inbound approach course without advising tower. Contributing factors were nerves, not thinking ahead, allowing check ride 'itis' to interfere with my planning and common sense. Not too smart to be tracking an approach course even on a VFR day, in contact with tower and reporting our position.
Original NASA ASRS Text
Title: A PLT ON A CFII RATING RIDE HAS THE INSPECTOR TRACK INBOUND ON THE VOR APCH RADIAL BEFORE RECEIVING A CLRNC FROM THE TWR TO DO SO. THERE WAS NO CONFLICT.
Narrative: IN THE PROCESS OF COMPLETING CFII CHK RIDE -- EXAMINER FLYING UNDER HOOD, I AM TEACHING PARTIAL PANEL SKILLS. EXAMINER ASKS TO BE VECTORED FOR A VOR RWY 10 APCH DPA. I GIVE VECTORS, CALL DUPAGE TWR TO RPT, AND RPT 5 MI SW INBOUND. FIRST, OUR POS WAS 10 MI SW. NEXT, I SHOULD HAVE TOLD DUPAGE TWR WE WERE TRACKING THE VOR COURSE INBOUND, BUT DID NOT. THERE WAS NO TFC INBOUND, TWR ADVISED TO CALL 2 MI OUT, VERIFIED OUR POS SW OF VOR. I CALLED 2 MI OUT AND WE LEVELED AT 1500 FT AND COMPLETED NORMAL LNDG WITHOUT DIFFICULTY. I SHOULD HAVE ADVISED DPA TWR WE WERE TRACKING THE VOR RADIAL INBOUND ON INITIAL CALL, BUT THEY DID NOT ASK, ONLY VERIFIED WE WERE SW WHICH I DID. I ALSO GAVE THEM THE WRONG MILEAGE RPT ON INITIAL CALL. WHILE NOT STRICTLY WRONG TO TRACK THE VOR TO ARPT ON GOOD VOR DAY, I SHOULD NOT HAVE TRACKED INBOUND APCH COURSE WITHOUT ADVISING TWR. CONTRIBUTING FACTORS WERE NERVES, NOT THINKING AHEAD, ALLOWING CHK RIDE 'ITIS' TO INTERFERE WITH MY PLANNING AND COMMON SENSE. NOT TOO SMART TO BE TRACKING AN APCH COURSE EVEN ON A VFR DAY, IN CONTACT WITH TWR AND RPTING OUR POS.
Data retrieved from NASA's ASRS site as of July 2007 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.