37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 96430 |
Time | |
Date | 198810 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : ccr |
State Reference | CA |
Altitude | msl bound lower : 800 msl bound upper : 850 |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | tower : ccr tower : den |
Operator | general aviation : instructional |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | descent : approach other |
Flight Plan | VFR |
Aircraft 2 | |
Operator | general aviation : instructional |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | other |
Person 1 | |
Affiliation | Other |
Function | instruction : instructor |
Qualification | pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 80 flight time total : 1300 flight time type : 250 |
ASRS Report | 96430 |
Person 2 | |
Affiliation | Other |
Function | instruction : trainee |
Qualification | pilot : private |
Events | |
Anomaly | conflict : nmac non adherence : clearance |
Independent Detector | other controllera other flight crewa |
Resolutory Action | flight crew : took evasive action other |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 250 vertical : 50 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Narrative:
I experienced a near miss on a circle to land from a lda approach into 19R at buchanan. During my entry into right downwind for runway 32R from my lda approach for runway 19R, I heard the controller say during my execution of a circle to land, 'small aircraft X cleared for touch and go on 32R, #4. Follow aircraft wide right base.' I responded, 'small aircraft X looking.' by this time I was on mid downwind. When I was almost abeam the tower on right downwind for 32R, I heard the controller say, 'small aircraft X, #2, follow aircraft short final.' I acknowledged, 'small aircraft X aircraft in sight.' my student and I had identified an aircraft on short final for runway 32R. Shortly after my response, the controller said, 'small aircraft X, you might want to angle out to the left.' I thought that he was referring to the fact that we were angling in towards the runway on the right downwind leg for runway 32R. It was at this point that I happened to check for traffic to my left and I saw traffic 200-300' away and 50' above us converging from my left and descending for a base entry. I instructed my student to deviate to the right and we started a right 180 degree turn from downwind onto final and added power to climb. Contributing factors were the position report of traffic given an the radio phraseology used. From my perspective, the aircraft was on a wide entry to right base rather than on a wide right base leg. The controller called out '#2,' confirmed by my student. I, however, happened to hear also '...follow aircraft short final,' after the '#2' phrase. I felt the controller could have given a more accurate position report and especially not called out '#2' with an aircraft on short final. Rather he should have called out '#3 for touch and go' with a better position report on traffic. I have not reported the incident as a near miss, but I spoke with the pilot of the other aircraft (also an instrument and student) and the instrument mentioned he had us in sight all along. Yet he didn't maneuver to avoid us until we took action and didn't inquire to the tower about us as we were converging. I called the tower over the phone and I spoke with the controller who was operating on the ground frequency at the time of the incident. He said some controllers will not count the traffic on short final, in terms of reporting the sequencing #. I intend to ask the supervisor of buchanan tower to listen to the tapes to verify the radio communication. The flight was my 1ST of the day and my student's only flight of the day. I felt, given the situation, I took the appropriate evasive action. I also feel I was not at fault given the information that I was given on my second communication about sequencing, but I think I could have given more thought to how my sequencing reduced so relatively quickly from #4 to #2 and how my traffic went from a wide ride base to a short final so quickly. I also realize now that it was possible the controller was referring to my following of the traffic when he said, 'small aircraft X, you might want to angle out to the left for traffic on right base,' that would have been a great help! The other aircraft was a high fixed wing tail dragger. I am unfamiliar with the make and model.
Original NASA ASRS Text
Title: SMA GIVEN SEQUENCE FOR TOUCH AND GO AND TRAFFIC TO FOLLOW. HAD WRONG ACFT IN SIGHT AND ENDED UP IN CLOSE PROX TO ACFT HE WAS TO FOLLOW.
Narrative: I EXPERIENCED A NEAR MISS ON A CIRCLE TO LAND FROM A LDA APCH INTO 19R AT BUCHANAN. DURING MY ENTRY INTO RIGHT DOWNWIND FOR RWY 32R FROM MY LDA APCH FOR RWY 19R, I HEARD THE CTLR SAY DURING MY EXECUTION OF A CIRCLE TO LAND, 'SMA X CLRED FOR TOUCH AND GO ON 32R, #4. FOLLOW ACFT WIDE RIGHT BASE.' I RESPONDED, 'SMA X LOOKING.' BY THIS TIME I WAS ON MID DOWNWIND. WHEN I WAS ALMOST ABEAM THE TWR ON RIGHT DOWNWIND FOR 32R, I HEARD THE CTLR SAY, 'SMA X, #2, FOLLOW ACFT SHORT FINAL.' I ACKNOWLEDGED, 'SMA X ACFT IN SIGHT.' MY STUDENT AND I HAD IDENTIFIED AN ACFT ON SHORT FINAL FOR RWY 32R. SHORTLY AFTER MY RESPONSE, THE CTLR SAID, 'SMA X, YOU MIGHT WANT TO ANGLE OUT TO THE LEFT.' I THOUGHT THAT HE WAS REFERRING TO THE FACT THAT WE WERE ANGLING IN TOWARDS THE RWY ON THE RIGHT DOWNWIND LEG FOR RWY 32R. IT WAS AT THIS POINT THAT I HAPPENED TO CHK FOR TFC TO MY LEFT AND I SAW TFC 200-300' AWAY AND 50' ABOVE US CONVERGING FROM MY LEFT AND DSNDING FOR A BASE ENTRY. I INSTRUCTED MY STUDENT TO DEVIATE TO THE RIGHT AND WE STARTED A RIGHT 180 DEG TURN FROM DOWNWIND ONTO FINAL AND ADDED POWER TO CLB. CONTRIBUTING FACTORS WERE THE POS RPT OF TFC GIVEN AN THE RADIO PHRASEOLOGY USED. FROM MY PERSPECTIVE, THE ACFT WAS ON A WIDE ENTRY TO RIGHT BASE RATHER THAN ON A WIDE RIGHT BASE LEG. THE CTLR CALLED OUT '#2,' CONFIRMED BY MY STUDENT. I, HOWEVER, HAPPENED TO HEAR ALSO '...FOLLOW ACFT SHORT FINAL,' AFTER THE '#2' PHRASE. I FELT THE CTLR COULD HAVE GIVEN A MORE ACCURATE POS RPT AND ESPECIALLY NOT CALLED OUT '#2' WITH AN ACFT ON SHORT FINAL. RATHER HE SHOULD HAVE CALLED OUT '#3 FOR TOUCH AND GO' WITH A BETTER POS RPT ON TFC. I HAVE NOT RPTED THE INCIDENT AS A NEAR MISS, BUT I SPOKE WITH THE PLT OF THE OTHER ACFT (ALSO AN INSTR AND STUDENT) AND THE INSTR MENTIONED HE HAD US IN SIGHT ALL ALONG. YET HE DIDN'T MANEUVER TO AVOID US UNTIL WE TOOK ACTION AND DIDN'T INQUIRE TO THE TWR ABOUT US AS WE WERE CONVERGING. I CALLED THE TWR OVER THE PHONE AND I SPOKE WITH THE CTLR WHO WAS OPERATING ON THE GND FREQ AT THE TIME OF THE INCIDENT. HE SAID SOME CTLRS WILL NOT COUNT THE TFC ON SHORT FINAL, IN TERMS OF RPTING THE SEQUENCING #. I INTEND TO ASK THE SUPVR OF BUCHANAN TWR TO LISTEN TO THE TAPES TO VERIFY THE RADIO COM. THE FLT WAS MY 1ST OF THE DAY AND MY STUDENT'S ONLY FLT OF THE DAY. I FELT, GIVEN THE SITUATION, I TOOK THE APPROPRIATE EVASIVE ACTION. I ALSO FEEL I WAS NOT AT FAULT GIVEN THE INFO THAT I WAS GIVEN ON MY SECOND COM ABOUT SEQUENCING, BUT I THINK I COULD HAVE GIVEN MORE THOUGHT TO HOW MY SEQUENCING REDUCED SO RELATIVELY QUICKLY FROM #4 TO #2 AND HOW MY TFC WENT FROM A WIDE RIDE BASE TO A SHORT FINAL SO QUICKLY. I ALSO REALIZE NOW THAT IT WAS POSSIBLE THE CTLR WAS REFERRING TO MY FOLLOWING OF THE TFC WHEN HE SAID, 'SMA X, YOU MIGHT WANT TO ANGLE OUT TO THE LEFT FOR TFC ON RIGHT BASE,' THAT WOULD HAVE BEEN A GREAT HELP! THE OTHER ACFT WAS A HIGH FIXED WING TAIL DRAGGER. I AM UNFAMILIAR WITH THE MAKE AND MODEL.
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.