Atx flight crew extra careful to report on unicom their position on approach and landing and then received late call from small aircraft landing same runway opposite direction.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	169939
Time
Date	199102
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : tup
State Reference	MS
Altitude	agl bound lower : 0 agl bound upper : 100
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Operator	common carrier : air taxi
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	landing other
Flight Plan	VFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	descent : approach landing other
Flight Plan	None
Person 1
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : commercial pilot : instrument
Experience	flight time last 90 days : 200 flight time total : 10800
ASRS Report	169939
Person 2
Affiliation	company : air taxi
Function	flight crew : first officer
Qualification	pilot : private pilot : commercial pilot : instrument
Events
Anomaly	conflict : ground critical
Independent Detector	other flight crewa
Resolutory Action	other
Consequence	Other
Miss Distance	horizontal : 0 vertical : 100
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was the captain on a scheduled carrier flight from ban to tup. Tup is an uncontrolled field, with no tower or FSS, just traffic advisory on unicom CTAF. Center reported no known traffic and cleared us for a visibility approach. Because we knew tub is uncontrolled, we started calling from 25 mi out for traffic advisories. We were told there was 'no known traffic.' we continued to call our position at 10 mi, 5 mi out, at downwind for runway 36, base, final, 1 mi final and short final. When we called on short final, an small aircraft reported to be 'short final to 18, tup.' we could not see him due to the haze and the sun going down, and by this time we were flaring for landing. We asked him if he had seen or heard us, and he stated, 'oh, yes, I heard you all those times but didn't think you were landing on 36.' he also stated he was executing a go around. During his go around, he flew very close to our aircraft, which was on the runway by then. This near incident was caused by this pilot not using proper CTAF procedures. If people don't call their position. They stand a good chance of having a midair!

Original NASA ASRS Text

Title: ATX FLT CREW EXTRA CAREFUL TO REPORT ON UNICOM THEIR POSITION ON APCH AND LNDG AND THEN RECEIVED LATE CALL FROM SMA LNDG SAME RWY OPPOSITE DIRECTION.

Narrative: I WAS THE CAPT ON A SCHEDULED CARRIER FLT FROM BAN TO TUP. TUP IS AN UNCONTROLLED FIELD, WITH NO TWR OR FSS, JUST TFC ADVISORY ON UNICOM CTAF. CENTER RPTED NO KNOWN TFC AND CLRED US FOR A VIS APCH. BECAUSE WE KNEW TUB IS UNCONTROLLED, WE STARTED CALLING FROM 25 MI OUT FOR TFC ADVISORIES. WE WERE TOLD THERE WAS 'NO KNOWN TFC.' WE CONTINUED TO CALL OUR POS AT 10 MI, 5 MI OUT, AT DOWNWIND FOR RWY 36, BASE, FINAL, 1 MI FINAL AND SHORT FINAL. WHEN WE CALLED ON SHORT FINAL, AN SMA RPTED TO BE 'SHORT FINAL TO 18, TUP.' WE COULD NOT SEE HIM DUE TO THE HAZE AND THE SUN GOING DOWN, AND BY THIS TIME WE WERE FLARING FOR LNDG. WE ASKED HIM IF HE HAD SEEN OR HEARD US, AND HE STATED, 'OH, YES, I HEARD YOU ALL THOSE TIMES BUT DIDN'T THINK YOU WERE LNDG ON 36.' HE ALSO STATED HE WAS EXECUTING A GAR. DURING HIS GAR, HE FLEW VERY CLOSE TO OUR ACFT, WHICH WAS ON THE RWY BY THEN. THIS NEAR INCIDENT WAS CAUSED BY THIS PLT NOT USING PROPER CTAF PROCS. IF PEOPLE DON'T CALL THEIR POS. THEY STAND A GOOD CHANCE OF HAVING A MIDAIR!

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.