37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 263996 |
Time | |
Date | 199402 |
Day | Thu |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : mkg |
State Reference | MI |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : mkg |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | landing other other |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Piper Single Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff landing other other |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : atp |
Experience | flight time last 90 days : 70 flight time total : 6500 flight time type : 2500 |
ASRS Report | 263996 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | conflict : ground critical incursion : landing without clearance non adherence : clearance non adherence : far other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : took evasive action none taken : insufficient time other |
Consequence | Other |
Miss Distance | horizontal : 100 vertical : 75 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We landed on runway 24 at mkg. Piper traffic was to make left traffic and tower would call downwind. He made right traffic and tear- dropped to runway 6. On rollout, opposing traffic less than 2000 ft and below 50 ft and closing. We saw him and turned off at the nearest taxiway. He continued and did a touch and go. The tower was distracted by traffic northeast and, after confirming piper would make left traffic and tower would call downwind, tower did not maintain visual with the piper. We had visual contact with the piper shortly after his takeoff, then lost it on short final. No one expected him to not do anything the tower told him. How often have you checked the opposing traffic's final approach on the runway you're landing on. Maybe we should be looking more often.
Original NASA ASRS Text
Title: AN SMA LANDED THE WRONG WAY, THEN TOOK EVASIVE ACTION TOUCH AND GO OVER AN ACR MDT ON ROLLOUT.
Narrative: WE LANDED ON RWY 24 AT MKG. PIPER TFC WAS TO MAKE L TFC AND TWR WOULD CALL DOWNWIND. HE MADE R TFC AND TEAR- DROPPED TO RWY 6. ON ROLLOUT, OPPOSING TFC LESS THAN 2000 FT AND BELOW 50 FT AND CLOSING. WE SAW HIM AND TURNED OFF AT THE NEAREST TXWY. HE CONTINUED AND DID A TOUCH AND GO. THE TWR WAS DISTRACTED BY TFC NE AND, AFTER CONFIRMING PIPER WOULD MAKE L TFC AND TWR WOULD CALL DOWNWIND, TWR DID NOT MAINTAIN VISUAL WITH THE PIPER. WE HAD VISUAL CONTACT WITH THE PIPER SHORTLY AFTER HIS TKOF, THEN LOST IT ON SHORT FINAL. NO ONE EXPECTED HIM TO NOT DO ANYTHING THE TWR TOLD HIM. HOW OFTEN HAVE YOU CHKED THE OPPOSING TFC'S FINAL APCH ON THE RWY YOU'RE LNDG ON. MAYBE WE SHOULD BE LOOKING MORE OFTEN.
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.