A C172 has a ground conflict with a landing extra 300 GA aircraft that attempted a long landing over...

Attributes
ACN	514108
Time
Date	200106
Day	Sat
Place
Locale Reference	airport : ump.airport
State Reference	IN
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : tcm.tower
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Plan	None
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	descent : approach landing : go around
Route In Use	approach : traffic pattern
Person 1
Affiliation	other
Function	flight crew : single pilot
ASRS Report	514108
Person 2
Affiliation	other
Function	flight crew : single pilot
Events
Anomaly	conflict : ground critical incursion : runway non adherence : far non adherence : published procedure non adherence : required legal separation other anomaly other anomaly other other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	flight crew : executed go around none taken : insufficient time
Miss Distance	horizontal : 0 vertical : 50
Supplementary
Problem Areas	Airport Airspace Structure Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was preparing to depart from ump in our cessna 172. The active runway was runway 33. The airport was very busy, since this was the best WX we had in several weeks and it was saturday morning -- ump is non twred. I was listening to CTAF 122.8 during taxi and run-up operations to become familiar with traffic in the pattern. Before departing, I had to wait around 5 mins due to 3 or 4 landing aircraft. Eventually, runway 33 was clear and the nearest landing aircraft (in the pattern) was on downwind for runway 33. I turned my plane to the east to scan for traffic, and heard the incoming traffic announce starting left base for runway 33. We could not see the airplane yet, and announced departing runway 33. I taxied onto the runway and before we could even complete our turn for runway alignment, the incoming plane announced 'cessna, hold short of runway 33 for landing traffic on short final!' this was 5-10 seconds after he had announced starting left base. I was turning my plane around to return to the taxiway when a shadow passed right by us and then I saw an extra 300 touch down on the runway. For whatever reason, he took off and made a go around, probably because he was going too fast and had landed slightly long. The extra 300 made a very close, fast pattern and came back and landed around 30 seconds later. I believe the following items contributed to this near miss: 1) the extra 300 was flying a nonstandard, close-in and fast traffic pattern, which did not conform with other existing traffic. 2) the airport was very busy at the time. 3) the extra 300 tried to land even though I had taxied onto the runway, instead of immediately going around. 4) the extra 300 pilot was very aggressive and inconsiderate of all other aircraft in the vicinity. Contributing factor: I had assumed other aircraft would be flying a standard traffic pattern (dimensionally) as defined in far/aim and other reference texts.

Original NASA ASRS Text

Title: A C172 HAS A GND CONFLICT WITH A LNDG EXTRA 300 GA ACFT THAT ATTEMPTED A LONG LNDG OVER THE C172 ON RWY AT UMP, IN.

Narrative: I WAS PREPARING TO DEPART FROM UMP IN OUR CESSNA 172. THE ACTIVE RWY WAS RWY 33. THE ARPT WAS VERY BUSY, SINCE THIS WAS THE BEST WX WE HAD IN SEVERAL WKS AND IT WAS SATURDAY MORNING -- UMP IS NON TWRED. I WAS LISTENING TO CTAF 122.8 DURING TAXI AND RUN-UP OPS TO BECOME FAMILIAR WITH TFC IN THE PATTERN. BEFORE DEPARTING, I HAD TO WAIT AROUND 5 MINS DUE TO 3 OR 4 LNDG ACFT. EVENTUALLY, RWY 33 WAS CLR AND THE NEAREST LNDG ACFT (IN THE PATTERN) WAS ON DOWNWIND FOR RWY 33. I TURNED MY PLANE TO THE E TO SCAN FOR TFC, AND HEARD THE INCOMING TFC ANNOUNCE STARTING L BASE FOR RWY 33. WE COULD NOT SEE THE AIRPLANE YET, AND ANNOUNCED DEPARTING RWY 33. I TAXIED ONTO THE RWY AND BEFORE WE COULD EVEN COMPLETE OUR TURN FOR RWY ALIGNMENT, THE INCOMING PLANE ANNOUNCED 'CESSNA, HOLD SHORT OF RWY 33 FOR LNDG TFC ON SHORT FINAL!' THIS WAS 5-10 SECONDS AFTER HE HAD ANNOUNCED STARTING L BASE. I WAS TURNING MY PLANE AROUND TO RETURN TO THE TXWY WHEN A SHADOW PASSED RIGHT BY US AND THEN I SAW AN EXTRA 300 TOUCH DOWN ON THE RWY. FOR WHATEVER REASON, HE TOOK OFF AND MADE A GAR, PROBABLY BECAUSE HE WAS GOING TOO FAST AND HAD LANDED SLIGHTLY LONG. THE EXTRA 300 MADE A VERY CLOSE, FAST PATTERN AND CAME BACK AND LANDED AROUND 30 SECONDS LATER. I BELIEVE THE FOLLOWING ITEMS CONTRIBUTED TO THIS NEAR MISS: 1) THE EXTRA 300 WAS FLYING A NONSTANDARD, CLOSE-IN AND FAST TFC PATTERN, WHICH DID NOT CONFORM WITH OTHER EXISTING TFC. 2) THE ARPT WAS VERY BUSY AT THE TIME. 3) THE EXTRA 300 TRIED TO LAND EVEN THOUGH I HAD TAXIED ONTO THE RWY, INSTEAD OF IMMEDIATELY GOING AROUND. 4) THE EXTRA 300 PLT WAS VERY AGGRESSIVE AND INCONSIDERATE OF ALL OTHER ACFT IN THE VICINITY. CONTRIBUTING FACTOR: I HAD ASSUMED OTHER ACFT WOULD BE FLYING A STANDARD TFC PATTERN (DIMENSIONALLY) AS DEFINED IN FAR/AIM AND OTHER REF TEXTS.

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.

A C172 has a ground conflict with a landing extra 300 GA aircraft that attempted a long landing over the C172 on runway at ump, in.