37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 425920 |
Time | |
Date | 199901 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : tul |
State Reference | OK |
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 | Fokker 100 |
Navigation In Use | Other |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Flight Phase | descent : approach |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
ASRS Report | 425920 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial |
ASRS Report | 425919 |
Events | |
Anomaly | aircraft equipment problem : critical non adherence : far non adherence other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Air Traffic Incident | Pilot Deviation |
Narrative:
Tul runway 36R. After gate departure, ATC issued us a flow control time to ord. Taxied to a hold area on 1 engine to conserve fuel. Started #2 engine and began the before takeoff checklist in time to make the flow time. As we were cleared onto the runway to hold, we had difficulty getting the normal indication on the left MFDU during the takeoff confign check. Verified all confign system were normal with no malfunctions indicated. Pushed the power up above minimum takeoff and did not get any takeoff confign warnings. With our flow control time about to expire and an aircraft on final for landing, I elected to take off. En route to ord, I researched the problem and determined that I probably should have returned to the gate and had maintenance check out the system. Landed ord without incident. Did additional takeoff confign checks during taxi in at ord and could not get the normal indication to appear on the left MFDU. Placed the discrepancy in the logbook.
Original NASA ASRS Text
Title: AN FK10 FLC PERFORMS A TKOF WITHOUT THEIR L MFDU DISPLAYING ANY INFO.
Narrative: TUL RWY 36R. AFTER GATE DEP, ATC ISSUED US A FLOW CTL TIME TO ORD. TAXIED TO A HOLD AREA ON 1 ENG TO CONSERVE FUEL. STARTED #2 ENG AND BEGAN THE BEFORE TKOF CHKLIST IN TIME TO MAKE THE FLOW TIME. AS WE WERE CLRED ONTO THE RWY TO HOLD, WE HAD DIFFICULTY GETTING THE NORMAL INDICATION ON THE L MFDU DURING THE TKOF CONFIGN CHK. VERIFIED ALL CONFIGN SYS WERE NORMAL WITH NO MALFUNCTIONS INDICATED. PUSHED THE PWR UP ABOVE MINIMUM TKOF AND DID NOT GET ANY TKOF CONFIGN WARNINGS. WITH OUR FLOW CTL TIME ABOUT TO EXPIRE AND AN ACFT ON FINAL FOR LNDG, I ELECTED TO TAKE OFF. ENRTE TO ORD, I RESEARCHED THE PROB AND DETERMINED THAT I PROBABLY SHOULD HAVE RETURNED TO THE GATE AND HAD MAINT CHK OUT THE SYS. LANDED ORD WITHOUT INCIDENT. DID ADDITIONAL TKOF CONFIGN CHKS DURING TAXI IN AT ORD AND COULD NOT GET THE NORMAL INDICATION TO APPEAR ON THE L MFDU. PLACED THE DISCREPANCY IN THE LOGBOOK.
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.