37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 257480 |
Time | |
Date | 199311 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : jpu |
State Reference | PA |
Altitude | msl bound lower : 2800 msl bound upper : 2800 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zid tower : ict |
Operator | common carrier : air carrier |
Make Model Name | Light Transport, High Wing, 2 Turboprop Eng |
Flight Phase | descent : approach descent other |
Route In Use | approach : straight in |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : cfi pilot : instrument |
Experience | flight time last 90 days : 200 flight time total : 6990 flight time type : 3000 |
ASRS Report | 257480 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | aircraft equipment problem : less severe |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : overcame equipment problem |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | other |
Narrative:
Flight was proceeding to shoot a VOR approach at pkb airport. About 4 NM from jpu VOR at 2800 ft, the following unusual incident occurred: 'in-flight: ailerons, aircraft would not turn to left. Click noise heard before ailerons freed. Flaps up (no ice, in clouds). This occurred 3 times prior to touchdown, once at 4 NM from jpu and twice from jpu to touchdown. Allowed first officer to continue approach and fly aircraft because problem easy to overcome by his words and actions, and wanted to get aircraft on the ground considering, narrative for incident report for NTSB 830 report on 'malfunction of flight controls' sent to chief pilot at company on wkend nov/xx/93 and told incident report would be filed and reported nov/mon/93. Report requires immediate notification to nearest NTSB. Air carrier airways procedures: chief pilot files/reports to FAA/NTSB. PIC or sic required to send narrative to chief pilot and director of maintenance and director of operations. Callback conversation with reporter revealed the following: reporter did not follow up as to the cause of binding. Aircraft is cable control and suspects it was out of rig. Aircraft did fly out on next sequence after maintenance had been performed.
Original NASA ASRS Text
Title: AILERON BINDING IN TURN TO L. LANDED OK.
Narrative: FLT WAS PROCEEDING TO SHOOT A VOR APCH AT PKB ARPT. ABOUT 4 NM FROM JPU VOR AT 2800 FT, THE FOLLOWING UNUSUAL INCIDENT OCCURRED: 'INFLT: AILERONS, ACFT WOULD NOT TURN TO L. CLICK NOISE HEARD BEFORE AILERONS FREED. FLAPS UP (NO ICE, IN CLOUDS). THIS OCCURRED 3 TIMES PRIOR TO TOUCHDOWN, ONCE AT 4 NM FROM JPU AND TWICE FROM JPU TO TOUCHDOWN. ALLOWED FO TO CONTINUE APCH AND FLY ACFT BECAUSE PROB EASY TO OVERCOME BY HIS WORDS AND ACTIONS, AND WANTED TO GET ACFT ON THE GND CONSIDERING, NARRATIVE FOR INCIDENT RPT FOR NTSB 830 RPT ON 'MALFUNCTION OF FLT CTLS' SENT TO CHIEF PLT AT COMPANY ON WKEND NOV/XX/93 AND TOLD INCIDENT RPT WOULD BE FILED AND RPTED NOV/MON/93. RPT REQUIRES IMMEDIATE NOTIFICATION TO NEAREST NTSB. ACR AIRWAYS PROCS: CHIEF PLT FILES/RPTS TO FAA/NTSB. PIC OR SIC REQUIRED TO SEND NARRATIVE TO CHIEF PLT AND DIRECTOR OF MAINT AND DIRECTOR OF OPS. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING: RPTR DID NOT FOLLOW UP AS TO THE CAUSE OF BINDING. ACFT IS CABLE CTL AND SUSPECTS IT WAS OUT OF RIG. ACFT DID FLY OUT ON NEXT SEQUENCE AFTER MAINT HAD BEEN PERFORMED.
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.