Reporter commences takeoff on wrong runway. Takeoff aborted at suggestion of tower.

Attributes
ACN	303235
Time
Date	199504
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : ilg
State Reference	DE
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Skylane 182/RG Turbo Skylane/RG
Operating Under FAR Part	Part 91
Flight Phase	ground other : taxi other
Flight Plan	None
Person 1
Affiliation	company : air carrier
Function	flight crew : single pilot
Qualification	pilot : private pilot : instrument
Experience	flight time last 90 days : 10 flight time total : 1368 flight time type : 400
ASRS Report	303235
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other other : unspecified atc
Resolutory Action	controller : issued new clearance other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation
Situations
Airport	other physical facility

Narrative:

Requested progressive taxi instructions from FBO to active. Instructed by ground to taxi straight ahead through hangar area to runway 14. Observed 'hold short' lines for runway 09 which intersects runway 14 at 50 degree angle. After runup (still holding short of runway 09), was cleared by tower for immediate departure on runway 14. Began takeoff roll on what I believed to be runway 14, and was told by tower to abort takeoff, as I was actually on runway 09. Immediately aborted takeoff and held short of intersecting runway 19. Shortly thereafter, cleared to takeoff on runway 19. No traffic conflicts, and no evasive action necessary. Analysis, contributing factors, recommendations: unfamiliarity with airport layout (reason for requesting progressive taxi). Pilot should obtain airport layout information prior to taxi, and inform ground if generally unfamiliar with area (this was done). Ground/tower should exercise diligence in visually following aircraft to desired point of departure. Pilot should exercise added diligence in observing visual aids to desired point of departure (runway signs, hold short lines, visual markers, etc.) if assigned takeoff runway is at unusual angle to feeder taxiway, and pilot is inexperienced with airport layout (and has informed ATC of this), ATC should take additional care in observing traffic to departure/termination point. Callback conversation with reporter revealed the following information: the reporter stated he was flying a cessna 182. He is an aviation insurance man who operates regularly to strange fields. The reporter stated he got the feeling with over 1000 hours of doing this sort of thing and in the business he is in and with his instrument training, he was pretty aware of good operating procedures and conscientious in applying them. He didn't think he would be one to goof in this manner. The experience was humbling, he said, and really got his attention. He said it made him slow down a bit and be more attentive to good operating practices like checking his heading when aligning with the runway for takeoffs and lndgs.

Original NASA ASRS Text

Title: RPTR COMMENCES TKOF ON WRONG RWY. TKOF ABORTED AT SUGGESTION OF TWR.

Narrative: REQUESTED PROGRESSIVE TAXI INSTRUCTIONS FROM FBO TO ACTIVE. INSTRUCTED BY GND TO TAXI STRAIGHT AHEAD THROUGH HANGAR AREA TO RWY 14. OBSERVED 'HOLD SHORT' LINES FOR RWY 09 WHICH INTERSECTS RWY 14 AT 50 DEG ANGLE. AFTER RUNUP (STILL HOLDING SHORT OF RWY 09), WAS CLRED BY TWR FOR IMMEDIATE DEP ON RWY 14. BEGAN TKOF ROLL ON WHAT I BELIEVED TO BE RWY 14, AND WAS TOLD BY TWR TO ABORT TKOF, AS I WAS ACTUALLY ON RWY 09. IMMEDIATELY ABORTED TKOF AND HELD SHORT OF INTERSECTING RWY 19. SHORTLY THEREAFTER, CLRED TO TKOF ON RWY 19. NO TFC CONFLICTS, AND NO EVASIVE ACTION NECESSARY. ANALYSIS, CONTRIBUTING FACTORS, RECOMMENDATIONS: UNFAMILIARITY WITH ARPT LAYOUT (REASON FOR REQUESTING PROGRESSIVE TAXI). PLT SHOULD OBTAIN ARPT LAYOUT INFO PRIOR TO TAXI, AND INFORM GND IF GENERALLY UNFAMILIAR WITH AREA (THIS WAS DONE). GND/TWR SHOULD EXERCISE DILIGENCE IN VISUALLY FOLLOWING ACFT TO DESIRED POINT OF DEP. PLT SHOULD EXERCISE ADDED DILIGENCE IN OBSERVING VISUAL AIDS TO DESIRED POINT OF DEP (RWY SIGNS, HOLD SHORT LINES, VISUAL MARKERS, ETC.) IF ASSIGNED TKOF RWY IS AT UNUSUAL ANGLE TO FEEDER TXWY, AND PLT IS INEXPERIENCED WITH ARPT LAYOUT (AND HAS INFORMED ATC OF THIS), ATC SHOULD TAKE ADDITIONAL CARE IN OBSERVING TFC TO DEP/TERMINATION POINT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED HE WAS FLYING A CESSNA 182. HE IS AN AVIATION INSURANCE MAN WHO OPERATES REGULARLY TO STRANGE FIELDS. THE RPTR STATED HE GOT THE FEELING WITH OVER 1000 HRS OF DOING THIS SORT OF THING AND IN THE BUSINESS HE IS IN AND WITH HIS INST TRAINING, HE WAS PRETTY AWARE OF GOOD OPERATING PROCS AND CONSCIENTIOUS IN APPLYING THEM. HE DIDN'T THINK HE WOULD BE ONE TO GOOF IN THIS MANNER. THE EXPERIENCE WAS HUMBLING, HE SAID, AND REALLY GOT HIS ATTN. HE SAID IT MADE HIM SLOW DOWN A BIT AND BE MORE ATTENTIVE TO GOOD OPERATING PRACTICES LIKE CHKING HIS HDG WHEN ALIGNING WITH THE RWY FOR TKOFS AND LNDGS.

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.