Air cargo aircraft crosses runway cleared to and lines up with wrong runway at mia.

Attributes
ACN	204245
Time
Date	199203
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : mia
State Reference	FL
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 80 flight time total : 7500 flight time type : 80
ASRS Report	204245
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial pilot : atp
Events
Anomaly	incursion : runway non adherence : clearance other anomaly other
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance flight crew : became reoriented
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Aircraft was taxiing on 'Q' at mia international preparing for takeoff on runway 27L. Switched to tower and was cleared for takeoff on runway 27. An medium large transport was parked at the approach end of runway 27. Our aircraft turned inside of medium large transport, inadvertently crossed runway 27 and lined up on runway 30 at mia. We realized the mistake, informed tower and held our position. We were subsequently cleared for takeoff on runway 30. Fatigue, confusing runway signs, unfamiliar with airport all played a role in the error. Tower personnel handled my mistake very professionally and no conflict with any other aircraft was experienced. Lesson: take more time, be extra cautions when unfamiliar with airport, especially when intersecting runways are so near to each other. Apparently no harm done, but violation of runway incursion makes you feel like an idiot! Unprofessional. Callback conversation with reporter revealed the following information: reporter states this was a stupid pilot error. (He made no excuses.) with some questioning, however, he stated this was a most unusual departure. Usually 12 or 9 runways in use at night for noise abatement. Fatigue also factor, 8TH day of 8 day schedule. Two jumpseat riders added distraction. Side ramp area, at night difficult to determine runway as taxi line crosses 27.

Original NASA ASRS Text

Title: AIR CARGO ACFT CROSSES RWY CLRED TO AND LINES UP WITH WRONG RWY AT MIA.

Narrative: ACFT WAS TAXIING ON 'Q' AT MIA INTL PREPARING FOR TKOF ON RWY 27L. SWITCHED TO TWR AND WAS CLRED FOR TKOF ON RWY 27. AN MLG WAS PARKED AT THE APCH END OF RWY 27. OUR ACFT TURNED INSIDE OF MLG, INADVERTENTLY CROSSED RWY 27 AND LINED UP ON RWY 30 AT MIA. WE REALIZED THE MISTAKE, INFORMED TWR AND HELD OUR POS. WE WERE SUBSEQUENTLY CLRED FOR TKOF ON RWY 30. FATIGUE, CONFUSING RWY SIGNS, UNFAMILIAR WITH ARPT ALL PLAYED A ROLE IN THE ERROR. TWR PERSONNEL HANDLED MY MISTAKE VERY PROFESSIONALLY AND NO CONFLICT WITH ANY OTHER ACFT WAS EXPERIENCED. LESSON: TAKE MORE TIME, BE EXTRA CAUTIONS WHEN UNFAMILIAR WITH ARPT, ESPECIALLY WHEN INTERSECTING RWYS ARE SO NEAR TO EACH OTHER. APPARENTLY NO HARM DONE, BUT VIOLATION OF RWY INCURSION MAKES YOU FEEL LIKE AN IDIOT! UNPROFESSIONAL. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THIS WAS A STUPID PLT ERROR. (HE MADE NO EXCUSES.) WITH SOME QUESTIONING, HOWEVER, HE STATED THIS WAS A MOST UNUSUAL DEP. USUALLY 12 OR 9 RWYS IN USE AT NIGHT FOR NOISE ABATEMENT. FATIGUE ALSO FACTOR, 8TH DAY OF 8 DAY SCHEDULE. TWO JUMPSEAT RIDERS ADDED DISTR. SIDE RAMP AREA, AT NIGHT DIFFICULT TO DETERMINE RWY AS TAXI LINE CROSSES 27.

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.