Aircraft cleared to land. On final given clearance to hold short of crossing runway. Did not hear cl...

Attributes
ACN	113545
Time
Date	198906
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : hya
State Reference	MA
Altitude	agl bound lower : 0 agl bound upper : 1000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : hya
Operator	common carrier : air carrier
Make Model Name	Light Transport
Flight Phase	landing other
Route In Use	approach : visual
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 6000 flight time type : 150
ASRS Report	113545
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Events
Anomaly	incursion : runway
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	other

Narrative:

After being cleared for a visual approach, we reported a 2 1/2-3 mi right base as requested by the tower. We were subsequently cleared to land on runway 24. We would be following touch and go traffic with minimal separation. After turning final, and while confirming our pre-landing checks were complete, the tower evidently cleared us to land on runway 24, but to hold short of intersecting runway 33/15. I do not recall this restriction to our landing clearance and subsequently rolled through the runway intersection. Because we had been following close behind traffic, and we were confirming pre-landing checks, I think that I was distracted enough to miss the second call from the tower completely. I feel that after a clearance has been given, changing said clearance on short final is not called for as often as is done by ATC. Also, when such a new clearance had been given, much stronger confirmation should be received concerning such a change. Callback conversation with reporter revealed the following: reporter states no conflict occurred due to crossing intersecting runway. Traffic was on at least 1 mi final and reporter's aircraft cleared in ample time. Feels tower controller was planning in case landing traffic was closer to touchdown.

Original NASA ASRS Text

Title: ACFT CLEARED TO LAND. ON FINAL GIVEN CLRNC TO HOLD SHORT OF CROSSING RWY. DID NOT HEAR CLRNC, DID NOT HOLD SHORT.

Narrative: AFTER BEING CLRED FOR A VISUAL APCH, WE REPORTED A 2 1/2-3 MI RIGHT BASE AS REQUESTED BY THE TWR. WE WERE SUBSEQUENTLY CLRED TO LAND ON RWY 24. WE WOULD BE FOLLOWING TOUCH AND GO TFC WITH MINIMAL SEPARATION. AFTER TURNING FINAL, AND WHILE CONFIRMING OUR PRE-LNDG CHECKS WERE COMPLETE, THE TWR EVIDENTLY CLRED US TO LAND ON RWY 24, BUT TO HOLD SHORT OF INTERSECTING RWY 33/15. I DO NOT RECALL THIS RESTRICTION TO OUR LNDG CLRNC AND SUBSEQUENTLY ROLLED THROUGH THE RWY INTXN. BECAUSE WE HAD BEEN FOLLOWING CLOSE BEHIND TFC, AND WE WERE CONFIRMING PRE-LNDG CHECKS, I THINK THAT I WAS DISTRACTED ENOUGH TO MISS THE SECOND CALL FROM THE TWR COMPLETELY. I FEEL THAT AFTER A CLRNC HAS BEEN GIVEN, CHANGING SAID CLRNC ON SHORT FINAL IS NOT CALLED FOR AS OFTEN AS IS DONE BY ATC. ALSO, WHEN SUCH A NEW CLRNC HAD BEEN GIVEN, MUCH STRONGER CONFIRMATION SHOULD BE RECEIVED CONCERNING SUCH A CHANGE. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING: REPORTER STATES NO CONFLICT OCCURRED DUE TO XING INTERSECTING RWY. TFC WAS ON AT LEAST 1 MI FINAL AND REPORTER'S ACFT CLRED IN AMPLE TIME. FEELS TWR CTLR WAS PLANNING IN CASE LNDG TFC WAS CLOSER TO TOUCHDOWN.

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.

Aircraft cleared to land. On final given clearance to hold short of crossing runway. Did not hear clearance, did not hold short.