Mdt had to abort takeoff when they received a takeoff warning horn.

Attributes
ACN	243659
Time
Date	199306
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : lga
State Reference	NY
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Transport, High Wing, 2 Turboprop Eng
Flight Phase	climbout : takeoff other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : instrument pilot : atp
Experience	flight time last 90 days : 200 flight time total : 12000 flight time type : 1000
ASRS Report	243659
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	aircraft equipment problem : less severe
Independent Detector	aircraft equipment other aircraft equipment : unspecified
Resolutory Action	flight crew : overcame equipment problem
Consequence	Other
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	other

Narrative:

During a normal flap 5 degree takeoff, we had the takeoff warning horn sound. We aborted, announced to tower that we had aborted, needed no assistance, and that we needed a few mins to chkout the system. We reset the flaps, which is usually the item that is causing the horn. We also checked and reset the trim, condition levers, and ecu. Added power at static position and got no horn. We then called maintenance control at our home base via operations and after some delay received their ok to depart. When we arrived, I called my operations duty manager to tell him what had happened. We had just received a new notice about these 'nuisance trips' and it was not totally clear as to what, if any, write-up we needed to do. I submitted a report to my chief pilot and asked for additional input. The crash, fire, and rescue trucks were out when we made our takeoff after talking with maintenance because that is the ny port authority's requirement. There was no problem at any time, and this horn goes off as soon as the power is advanced toward 'takeoff power.' in the past, up until may/93, we had only to reset the flaps and advance the power to verify the system was working properly and then depart, without any input from maintenance.

Original NASA ASRS Text

Title: MDT HAD TO ABORT TKOF WHEN THEY RECEIVED A TKOF WARNING HORN.

Narrative: DURING A NORMAL FLAP 5 DEG TKOF, WE HAD THE TKOF WARNING HORN SOUND. WE ABORTED, ANNOUNCED TO TWR THAT WE HAD ABORTED, NEEDED NO ASSISTANCE, AND THAT WE NEEDED A FEW MINS TO CHKOUT THE SYS. WE RESET THE FLAPS, WHICH IS USUALLY THE ITEM THAT IS CAUSING THE HORN. WE ALSO CHKED AND RESET THE TRIM, CONDITION LEVERS, AND ECU. ADDED PWR AT STATIC POS AND GOT NO HORN. WE THEN CALLED MAINT CTL AT OUR HOME BASE VIA OPS AND AFTER SOME DELAY RECEIVED THEIR OK TO DEPART. WHEN WE ARRIVED, I CALLED MY OPS DUTY MGR TO TELL HIM WHAT HAD HAPPENED. WE HAD JUST RECEIVED A NEW NOTICE ABOUT THESE 'NUISANCE TRIPS' AND IT WAS NOT TOTALLY CLR AS TO WHAT, IF ANY, WRITE-UP WE NEEDED TO DO. I SUBMITTED A RPT TO MY CHIEF PLT AND ASKED FOR ADDITIONAL INPUT. THE CRASH, FIRE, AND RESCUE TRUCKS WERE OUT WHEN WE MADE OUR TKOF AFTER TALKING WITH MAINT BECAUSE THAT IS THE NY PORT AUTHORITY'S REQUIREMENT. THERE WAS NO PROB AT ANY TIME, AND THIS HORN GOES OFF AS SOON AS THE PWR IS ADVANCED TOWARD 'TKOF PWR.' IN THE PAST, UP UNTIL MAY/93, WE HAD ONLY TO RESET THE FLAPS AND ADVANCE THE PWR TO VERIFY THE SYS WAS WORKING PROPERLY AND THEN DEPART, WITHOUT ANY INPUT FROM MAINT.

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.