Aircraft landing hwv touches down before previous arrival clears the runway.

Attributes
ACN	596620
Time
Date	200310
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : hwv.airport
State Reference	NY
Altitude	agl bound upper : 400
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Small Aircraft, Low Wing, 1 Eng, Retractable Gear
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	landing : roll
Flight Plan	None
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 200 flight time total : 23000 flight time type : 110
ASRS Report	596620
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : far non adherence : required legal separation
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact none taken : anomaly accepted
Miss Distance	horizontal : 2000
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

While practicing touch and goes I inadvertently landed on a runway that was still occupied by a previously landing aircraft. I was #2 on final with the aircraft ahead in sight. Spacing was good. I observed that aircraft touch down and roll out. I then went momentarily (heads down) to rechk landing confign (gear down, etc) at 400 ft MSL and 1/2 mi out. I was then again visual with the runway. All appeared normal and a normal landing was made. During rollout I noticed the aircraft at the far end of the runway. The runway itself is 4200 ft long, and there was no need for any evasive action. The planes were never closer than 2000 ft at taxi speed. Contributing factors were: the mindset that the aircraft would exit the runway in ample time for me to land. The fact that I lost sight of the plane during my heads down confign check. The fact that when I looked back at the runway, I focused on the touchdown zone and not the entire runway. That runway 15-33 at hwv is a light colored concrete runway and the plane I followed was also light colored thereby did not provide much contrast to catch my attention at the far end of the runway. I feel visually confirming the aircraft had exited the runway, rather than assuming it did, would have prevented the situation.

Original NASA ASRS Text

Title: ACFT LNDG HWV TOUCHES DOWN BEFORE PREVIOUS ARR CLRS THE RWY.

Narrative: WHILE PRACTICING TOUCH AND GOES I INADVERTENTLY LANDED ON A RWY THAT WAS STILL OCCUPIED BY A PREVIOUSLY LNDG ACFT. I WAS #2 ON FINAL WITH THE ACFT AHEAD IN SIGHT. SPACING WAS GOOD. I OBSERVED THAT ACFT TOUCH DOWN AND ROLL OUT. I THEN WENT MOMENTARILY (HEADS DOWN) TO RECHK LNDG CONFIGN (GEAR DOWN, ETC) AT 400 FT MSL AND 1/2 MI OUT. I WAS THEN AGAIN VISUAL WITH THE RWY. ALL APPEARED NORMAL AND A NORMAL LNDG WAS MADE. DURING ROLLOUT I NOTICED THE ACFT AT THE FAR END OF THE RWY. THE RWY ITSELF IS 4200 FT LONG, AND THERE WAS NO NEED FOR ANY EVASIVE ACTION. THE PLANES WERE NEVER CLOSER THAN 2000 FT AT TAXI SPD. CONTRIBUTING FACTORS WERE: THE MINDSET THAT THE ACFT WOULD EXIT THE RWY IN AMPLE TIME FOR ME TO LAND. THE FACT THAT I LOST SIGHT OF THE PLANE DURING MY HEADS DOWN CONFIGN CHK. THE FACT THAT WHEN I LOOKED BACK AT THE RWY, I FOCUSED ON THE TOUCHDOWN ZONE AND NOT THE ENTIRE RWY. THAT RWY 15-33 AT HWV IS A LIGHT COLORED CONCRETE RWY AND THE PLANE I FOLLOWED WAS ALSO LIGHT COLORED THEREBY DID NOT PROVIDE MUCH CONTRAST TO CATCH MY ATTN AT THE FAR END OF THE RWY. I FEEL VISUALLY CONFIRMING THE ACFT HAD EXITED THE RWY, RATHER THAN ASSUMING IT DID, WOULD HAVE PREVENTED THE SIT.

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.