A319 Captain reported a fume event that initially was signed off by Maintenance reoccurred on subsequent flight. The subsequent fume event was correctly diagnosed and repaired at next destination.

Date: 2022-11 · Aircraft: A319 · Phase: descent

Anomalies: aircraft-equipment-problem-less-severe|deviation-discrepancy-procedural-maintenance|deviation-discrepancy-procedural-published-material-policy|flight-deck-cabin-aircraft-event-smoke-fire-fumes-odor

Synopsis

A319 Captain reported a fume event that initially was signed off by Maintenance reoccurred on subsequent flight. The subsequent fume event was correctly diagnosed and repaired at next destination.

Narrative

When we arrived at the gate the lead FA (Flight Attendant) informed me that we had an odor/fume event. The lead didn't inform me during the flight as it occurred below 10;000 ft. and by the time it was confirmed by the rest of the inflight team the gear was down and we were landing. He stated that it was a 'dirty sock' smell. Per the FAR and SOP; this action was documented on the program and appropriate report.Local Maintenance Personnel arrived and attempted to find the source of the odor. They worked with the FA to look in the rear of the aircraft since that is where it started. Local Maintenance didn't appear to have any paperwork or task cards showing them what to do. They then decided that it was caused by the APU. I told them the APU wasn't running during the event. The local Maintenance Personnel commented that they didn't have a spare here and didn't want us to get stuck in ZZZ. Maintenance then decided to do an engine run to 'clear the system' and get us 'back on time'. I thought these were odd comments since all the procedures need to be accomplished in order. Since this was going to take a while and the FA were visibly shaken by the event and Maintenance attitude; I had them come to the terminal for fresh air and to get some food. The FO (First Officer) elected to stay with the aircraft. He informed me that Maintenance ran the engine and the cowls were never opened. The logbook was completed and the APU was placed on deferral.After getting the appropriate sign off; we proceeded back to ZZZ1. On descent at 10;000 ft. we again got the odor. Since the FA were already familiar; they chimed us during sterile. I ran the Elimination of Odor/Fumes procedure from the QRH. It was worse on this event and we could detect the smell in the cockpit. It wasn't a true 'dirty sock' and more of a chemical smell. This was again documented on the program and appropriate report. Due to the severity of this event (and adverse reactions); the FA called for medical assistance. They were recommended to visit the emergency room upon describing their symptoms. The FO and I also had our systems documented but we only were suffering from burning eyes that cleared up once we departed the aircraft.While describing the conditions to local Maintenance in ZZZ1; I noticed that he had a worksheet to determine the proper course of action. The worksheet he was using directed him to look for fluid leaks and to open the engine cowls. Upon opening the cowl he found a large amount of oil that should not be there. Since we had burning eyes and a chemical smell; he concluded that this oil was making its way into the bleed system. I assisted with some engine runs and then was released from duty.I am making this report because; in my opinion; it appears that local Maintenance in ZZZ may not have utilized the proper procedures to return the aircraft back to service as quickly as possible. This caused us to have a second event that lead to injuries to the crew. It is also my opinion; that these procedures may have been skipped or abbreviated to get the aircraft to leave ZZZ. I am basing this on my observations between the procedure difference between ZZZ and ZZZ1.Per SOP and the FAR's I documented these events in the program and received a sign-off before departing ZZZ. I also apologize for the delay in making this report; I was unaware of the proper way to document these issues and was waiting for guidance on how to proceed with this event.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.