37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1702785 |
Time | |
Date | 201911 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | A319 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Flight was a functional flight check to investigate vibrations reported by multiple crews on [the aircraft]. Maintenance had accomplished multiple maintenance repairs. They showed me all their documentation as well as a balanced aml and the spotting message. The ioc duty chief pilot walked me through FM; and dispatch and [maintenance control] briefed me on the spotting message. [The] maintainer gave us a thorough walk around and briefing on what we would be looking and listening for. We then could not sign in on cci due to our location at clt. My sharp copilot first officer (first officer); called ioc and had them talk us through signing in through our smart phones.we finally taxied about 38 minutes late. Climbout was normal but busy as my first officer was pilot flying; and I was coordinating with ATC for an altitude and route that would allow us to run the tests. The filed route by dispatch would not work. We were both coordinating with the technician on the jump seat as we investigated the vibrations. Just about top of climb; FL300; I noticed a printer message. Much to my surprise; it was a reassignment from tracking; or additional flying as it is now called. [The first officer] and I ignored it and almost on cue the vibrations and noises started as we were leveling off. We flew the rest of the [flight check]; compiling with ATC and [the maintainer's] requests; and landed uneventfully. I realize that ioc scheduling is in crisis mode most of the time. However; tracking must not ever reschedule or add flying to pilots on a functional check flight. These flights are not the norm for line and reserve pilots and can be very busy and even stressful. I was behind due to multiple delays as mentioned above. Before we even started engines; I told [the first officer] and [the maintainer] we would not rush. Do not reschedule or add flying to [flight check] crews.
Original NASA ASRS Text
Title: A319 Captain reported aircraft vibration and noise due to unknown cause during a flight check following a difficulty in signing in for duty and an attempt by Scheduling for additional flying.
Narrative: Flight was a functional flight check to investigate vibrations reported by multiple crews on [the aircraft]. Maintenance had accomplished multiple maintenance repairs. They showed me all their documentation as well as a balanced AML and the spotting message. The IOC Duty Chief Pilot walked me through FM; and Dispatch and [Maintenance Control] briefed me on the spotting message. [The] Maintainer gave us a thorough walk around and briefing on what we would be looking and listening for. We then could not sign in on CCI due to our location at CLT. My sharp copilot FO (First Officer); called IOC and had them talk us through signing in through our smart phones.We finally taxied about 38 minutes late. Climbout was normal but busy as my FO was Pilot Flying; and I was coordinating with ATC for an altitude and route that would allow us to run the tests. The filed route by Dispatch would not work. We were both coordinating with the Technician on the jump seat as we investigated the vibrations. Just about top of climb; FL300; I noticed a printer message. Much to my surprise; it was a reassignment from tracking; or additional flying as it is now called. [The FO] and I ignored it and almost on cue the vibrations and noises started as we were leveling off. We flew the rest of the [Flight Check]; compiling with ATC and [the Maintainer's] requests; and landed uneventfully. I realize that IOC Scheduling is in crisis mode most of the time. However; tracking MUST NOT ever reschedule or add flying to pilots on a functional check flight. These flights are NOT the norm for line and reserve pilots and can be very busy and even stressful. I was behind due to multiple delays as mentioned above. Before we even started engines; I told [the FO] and [the Maintainer] we would NOT rush. DO NOT RESCHEDULE OR ADD FLYING TO [FLIGHT CHECK] CREWS.
Data retrieved from NASA's ASRS site 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.