37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 105828 |
Time | |
Date | 198902 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : hut |
State Reference | KS |
Altitude | msl bound lower : 2080 msl bound upper : 2080 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : hut tower : iah |
Operator | common carrier : air carrier |
Make Model Name | Small Transport, Low Wing, 2 Turboprop Eng |
Flight Phase | descent : approach |
Flight Plan | None |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer observation : company check pilot |
Qualification | pilot : cfi pilot : atp |
Experience | flight time last 90 days : 65 flight time total : 6730 flight time type : 4710 |
ASRS Report | 105828 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : far non adherence : clearance other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Hut approach control had requested that we 'call the tower' at the VOR inbound. We had previously been cleared for the VOR runway 3 approach, circle-to-land runway 13. Approximately 2 mi southwest of the field, approach called reminding me to contact the tower. It was clear from this tone that he was annoyed. The only other traffic operating in the area (known to us) was another training flight making a 'low approach' to runway 13. He passed well below and in front of us. I failed to make the required call at the VOR because I allowed myself to become distracted by events in the vicinity of the final approach fix (VOR). I was conducting a type rating chkride under FAA authority as a designated pilot examiner. The applicant was performing marginally. I was preoccupied with monitoring his performance. I attribute the incident, in part, to fatigue--I had already put in a full day. The main breakdown, however, must rest with the apparently ineffective way in which I managed my resources. I should have made my call first--perhaps actually a little outside the fix. A mile one way or the other would not have made much difference to approach (they are non radar). I would then have been free to concentrate my attention on monitoring the applicant's performance. I did things backwards. An unfortunate coincidence of events right over the FAF pulled my attention away from non flying duties. The required call was lost when I let it get out of sequence.
Original NASA ASRS Text
Title: GA SMT ON TRAINING FLT FAILS TO CALL TWR AT FAF AS INSTRUCTED.
Narrative: HUT APCH CTL HAD REQUESTED THAT WE 'CALL THE TWR' AT THE VOR INBND. WE HAD PREVIOUSLY BEEN CLRED FOR THE VOR RWY 3 APCH, CIRCLE-TO-LAND RWY 13. APPROX 2 MI SW OF THE FIELD, APCH CALLED REMINDING ME TO CONTACT THE TWR. IT WAS CLEAR FROM THIS TONE THAT HE WAS ANNOYED. THE ONLY OTHER TFC OPERATING IN THE AREA (KNOWN TO US) WAS ANOTHER TRNING FLT MAKING A 'LOW APCH' TO RWY 13. HE PASSED WELL BELOW AND IN FRONT OF US. I FAILED TO MAKE THE REQUIRED CALL AT THE VOR BECAUSE I ALLOWED MYSELF TO BECOME DISTRACTED BY EVENTS IN THE VICINITY OF THE FINAL APCH FIX (VOR). I WAS CONDUCTING A TYPE RATING CHKRIDE UNDER FAA AUTHORITY AS A DESIGNATED PLT EXAMINER. THE APPLICANT WAS PERFORMING MARGINALLY. I WAS PREOCCUPIED WITH MONITORING HIS PERFORMANCE. I ATTRIBUTE THE INCIDENT, IN PART, TO FATIGUE--I HAD ALREADY PUT IN A FULL DAY. THE MAIN BREAKDOWN, HOWEVER, MUST REST WITH THE APPARENTLY INEFFECTIVE WAY IN WHICH I MANAGED MY RESOURCES. I SHOULD HAVE MADE MY CALL FIRST--PERHAPS ACTUALLY A LITTLE OUTSIDE THE FIX. A MILE ONE WAY OR THE OTHER WOULD NOT HAVE MADE MUCH DIFFERENCE TO APCH (THEY ARE NON RADAR). I WOULD THEN HAVE BEEN FREE TO CONCENTRATE MY ATTN ON MONITORING THE APPLICANT'S PERFORMANCE. I DID THINGS BACKWARDS. AN UNFORTUNATE COINCIDENCE OF EVENTS RIGHT OVER THE FAF PULLED MY ATTN AWAY FROM NON FLYING DUTIES. THE REQUIRED CALL WAS LOST WHEN I LET IT GET OUT OF SEQUENCE.
Data retrieved from NASA's ASRS site as of August 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.