A B767 flight crew in position and hold notice a BE58 land over the top of them on runway 26L at atl...

Attributes
ACN	627887
Time
Date	200408
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : atl.airport
State Reference	GA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Phase	ground : position and hold
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : atl.tower
Operator	general aviation : personal
Make Model Name	Beechcraft, Beech Aircraft Corp Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : flight engineer pilot : commercial
Experience	flight time last 90 days : 250 flight time type : 2000
ASRS Report	627887
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	conflict : ground critical incursion : runway non adherence : clearance non adherence : far
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 0 vertical : 75
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were cleared position and hold on runway 26L at atl. Several mins later a beech baron appeared in front of us preparing to land on runway 26L. It touched down 300-400 ft down the runway on centerline. There was a separate frequency for arrs (runway 26R) and one for departures (runway 26L). No radio calls were heard regarding the baron. I queried the tower as to what had happened. The response was that they were looking into it. I found out later that the baron had been cleared to land on runway 26R, but had lined up on runway 27R. He had been told to adjust to the north runway, but mistook runway 26L for the one he had been assigned (runway 26R). After he cleared the runway and a few mins had passed, we were cleared for takeoff. An otherwise uneventful trip.

Original NASA ASRS Text

Title: A B767 FLT CREW IN POS AND HOLD NOTICE A BE58 LAND OVER THE TOP OF THEM ON RWY 26L AT ATL.

Narrative: WE WERE CLRED POS AND HOLD ON RWY 26L AT ATL. SEVERAL MINS LATER A BEECH BARON APPEARED IN FRONT OF US PREPARING TO LAND ON RWY 26L. IT TOUCHED DOWN 300-400 FT DOWN THE RWY ON CTRLINE. THERE WAS A SEPARATE FREQ FOR ARRS (RWY 26R) AND ONE FOR DEPS (RWY 26L). NO RADIO CALLS WERE HEARD REGARDING THE BARON. I QUERIED THE TWR AS TO WHAT HAD HAPPENED. THE RESPONSE WAS THAT THEY WERE LOOKING INTO IT. I FOUND OUT LATER THAT THE BARON HAD BEEN CLRED TO LAND ON RWY 26R, BUT HAD LINED UP ON RWY 27R. HE HAD BEEN TOLD TO ADJUST TO THE N RWY, BUT MISTOOK RWY 26L FOR THE ONE HE HAD BEEN ASSIGNED (RWY 26R). AFTER HE CLRED THE RWY AND A FEW MINS HAD PASSED, WE WERE CLRED FOR TKOF. AN OTHERWISE UNEVENTFUL TRIP.

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.