elihoole/asrs-aviation-reports huggingface dataset:
Date: 201808
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: Airbus 318/319/320/321 Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Chip Detector
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Ambiguous

Narrative: I am submitting this [report] as informational. [A mechanic said] he has serious concerns about contract maintenance being performed in ZZZZ. He stated the following: that he worked on Aircraft X after it returned to ZZZ after left engine oil loss. He was assigned to investigate the oil loss and discovered the Chip Detector o-ring had been installed incorrectly (when installed incorrectly one can see green indicating improper installation) and when he followed up with [Maintenance Control] he discovered the Chip Detector and o-ring had been serviced in ZZZZ. I asked why is he telling me this so much later after the event and he said 'because it just happened again today on Aircraft Y'. He went on to state: he got involved today on Aircraft Y because ZZZ mechanics were investigating an engine oil leak after the aircraft returned to the airport and it seemed familiar to him. Upon further investigation and experience they found the Oil Filter Drain Plug o-ring improperly installed and once again green was showing. He went on to state the aircraft had the work card performed in station ZZZZ by contract maintenance.According to the ZZZ mechanic; he expressed the contractor in ZZZZ either lacks the training or skill level necessary to safely complete the chip detector cards on Airbus aircraft. He explained the housing is aluminum and that the mechanics in ZZZZ may be applying too much torque to the detector when it is installed in the housing.Ensure training of contract maintenance and FAA oversight of contract maintenance is on par with what is required of [the company] in the United States. He also stated that maybe the contractors are not applying the correct torque due to the specified torque value not being converted correctly.




Synopsis: Airbus A320 Series Technician reported that aircraft maintained by foreign contractor have excessive oil loss due to improper maintenance.
Date: 201309
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Rain; 10
Light: Daylight
Aircraft: Piper Single Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Sea; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Weather; Procedure; Airport
Primary problem: Ambiguous

Narrative: Aircraft incident - aircraft rollover - pilot single occupant - No injuries. Deteriorating landing surface at remote airstrip. Flooded runway condition due to recent record rains causing flooded landing surface conditions. NOAA NWS reported record recent precipitation in area. Low speed landing roll encountering excessively soft/flooded landing surface resulting in aircraft rollover. Minor/repairable aircraft damage. No injuries to pilot single occupant.




Synopsis: A PA-12 pilot performed a low speed landing roll but encountered an excessively soft/flooded landing surface resulting in aircraft rollover. Minor/repairable aircraft damage.
Date: 201906
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Situational Awareness
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Ground Event / Encounter Other / Unknown
Detector: Person Maintenance
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Fueling company has two very old fuel trucks that produce foul smoke. Due to the consistence of the trade winds the smoke blows directly into the cargo pits and work areas of the engine and landing gear. Smoke is also is ingested into the cabin; through the packs and pits; as the recirc fan intakes are located in the pit. This poses a health threat to all ground workers in the area as well as our customers. Our employees are feeling headaches; having trouble breathing; and feeling faint.




Synopsis: Maintenance Personnel reported fuel truck exhaust creating unhealthy working conditions to the ground personnel as well as onboard passengers.
Date: 202010
Local time of day: 0001-0600
Location: ZZZ.Tower, US
Flight conditions: VMC
Light: Daylight
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Airspeed Indicator
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew FLC Overrode Automation; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Manuals; Procedure
Primary problem: Manuals

Narrative: After takeoff EICAS message IAS DISAGREE and other associated messages. Erroneous airspeed indications. Blocked Captains pitot tube. Manually flew the aircraft. Returned to ZZZ after completing checklist.While conducting the checklist; the checklist says to refer to Flight with Unreliable Airspeed table in the performance inflight chapter. During this emergency; I was flying the airplane manually and was not able to assist the First Officer much with the checklist. If the table in the performance inflight chapter could be incorporated into the emergency checklist; this would reduce much of the stress of the situation and allow for a safer operation in an emergency situation.




Synopsis: After returning to departure airport with unreliable airspeed indication; the Captain suggested moving necessary charts to the relevant portion of the QRH for ease in location and use.
Date: 201912
Local time of day: 1201-1800
Location: SEA.Airport, WA
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp SEA
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Chart Or Publication
Primary problem: Chart Or Publication

Narrative: We arrived in Seattle with no incident. We were originally assigned Cargo 7 line 2W. Due to my unfamiliar with the new Cargo 7 parking lines; I spun the nose of the aircraft in the wrong direction (I had us facing south; while we were supposed to go east). While we were letting Seattle South Ramp Control know of our situation; Operations switched us to Cargo 7 line 4E. That allowed us to move straight ahead and then a left turn into our parking spot. The new Cargo 7 parking lines aren't in the Comply 365 Airport Info Charts yet. While they are in the Jepp charts; the layout can be vague for someone not familiar with the layout. Updating the airport info chart will help with these situations.




Synopsis: Air Carrier Captain reported a ramp incursion due to inadequate ramp chart.
Date: 201707
Local time of day: 0601-1200
Location: LAX.Airport, CA
Flight conditions: VMC
Light: Dawn
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B LAX
ATC / advisory: Tower LAX
Second aircraft: B777 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; Captain
Anomaly: Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: I was the pilot flying for the visual approach at the end of an [all night] flight. We were on vectors to final for runway 24R from a right base. During the final course intercept; I turned off the autopilot to fly slightly above the wake from the B777 we were following. The sun was just above the horizon making the B777 traffic and runways difficult to see in the LA haze. During the LOC intercept; I hit the B777 wake and I rolled to wings level to recover; this delayed the turn enough for me to overshoot the LOC to the south. After getting back into clear air; I started a harder than normal turn to final to correct for the overshoot. During the turn; the CA assisted my correction as he had traffic on final to the south complex in sight. At some point in the turn we received a momentary TA from the traffic to our south. After getting back on the LOC; the remainder of the approach and landing were uneventful.


Second narrative: Just prior to JETSA; following a B777; encountered the wake at 2200 ft. FO flying; flew [through] the localizer and well south of 24L. I took the airplane and flew the jet back onto the localizer where the aircraft was on a stabilized approach; transferred control back to the FO; landed [without] incident.


Synopsis: B737 flight crew reported a track deviation resulted when they encountered wake turbulence on a visual approach to LAX in trail of a B777.
Date: 202102
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise; Descent
Airspace: Class B ZZZ
Aircraft component: Hydraulic Main System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise descent; HYD 3 ELEV OFF level 1 illuminated. HYD 3 had 4.5. We referenced the QRH LEVEL 1 section. While still referencing the level 1 checklist; the HYD 3 QTY decreased to 4.2. Because we knew a HYD 3 FAIL was coming; we referenced the QRH HYD 3 FAIL checklist. I [advised ATC] and because we were so close to ZZZ; we continued on to ZZZ. As I was the pilot monitoring; First Officer and I traded duties making me pilot flying. We asked for and we're given direct to ZZZZZ For a visual to Runway XX. We slowed to 230 kts. around 20 miles from ZZZ and extended the gear before a failure occurred. QTY was 3.0. The gear extended fully and a HYD 3 FAIL level 2 alert followed. QTY 3 was now 0.4. Because we had already reviewed the QRH; we knew what we would have and not have for configuration. First Officer ran the HYD 3 FAIL checklist. Slats and flaps extended fully and we made a 35/extend landing with manual brakes. We notified ZZZ approach that we would shut down on Runway XX. We also confirmed this with ZZZ tower. We stopped and shutdown. ZZZ fire trucks circled the jet and said all looked OK. Maintenance came and towed us to Gate.


Second narrative: [Report narrative contained no additional information.]


Synopsis: Flight Crew reported making a precautionary landing after loss of number three Hydraulic system.
Date: 201901
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: Cloudy; .5
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Regained Aircraft Control
Contributing factors: Weather
Primary problem: Weather

Narrative: During our arrival into ZZZ area we were told that ILS XX was being used due to current weather conditions; which were 1/2 mi; 500 OVC.ATIS reported 4/4/4 and tower reported on short final that conditions turned to 3/3/3 but that a CRJ200 previously landed reporting good braking action. Tower instructed us to make left turn at the end of the runway; into runway XY. During the turn; the nose wheel became unresponsive and nose slipped off the runway.Tower and flight attendants were notified. The latter also confirmed that passengers were fine; with no reported injuries. Passengers were eventually deplaned and transported to the terminal.FO (First Officer) performed walk around and did not find any apparent damage to aircraft. No impact to any objects on ground.


Second narrative: [Report narrative contained no additional information.]


Synopsis: CRJ-900 flight crew reported sliding off pavement while attempting to exit the runway.
Date: 201310
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Cabin Furnishing
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Parts / Stores Personnel
Human factors: Communication Breakdown; Confusion; Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: QA audit wrote shop up for material on hand with vendor expiration dates past. Historically [computer program] used to determine [company] shelf life. Per [company document] life not established or not controlled. My supervisor has ordered the shop to disregard [company] shelf life and go by vendor expiration dates. The material in question is mostly shrink tubing. Sign off sheets have been established to check vendor expiration dates and sign off that this has been accomplished. An area that contains non packaged 4 foot long material (with NO way I can see to establish shelf life ) was recently sign- off as checked. Additionally I have asked Engineering about non stock purchased material and shelf life. Some of this tubing is marked and then cut up and stored in individual boxes for later use to identify parts of harness. Does shelf life matter here?




Synopsis: Company shop personnel are finding it difficult to determine the procedure for ascertaining product shelf life.
Date: 202201
Location: ZZZ.Airport, US
Flight conditions: Mixed
Aircraft: Commercial Fixed Wing
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Event / Encounter Weather / Turbulence
Detector: Person Flight Attendant
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Procedure; Human Factors; Airport; Weather
Primary problem: Weather

Narrative: Upon taxi in to the gate in IND the aircraft hit a patch of black ice and we slid across runway apparently hitting some ground lights on the way. We were told later we were not the first plane to do so. I was confused as to why our pilot was not informed of this upon arrival. The A flight attendant was shaken up as were other passengers up front more so as they got the brunt of the [event].Proper communication next time from the tower would have assisted us in avoiding this [event].




Synopsis: Commercial flight attendant reported the aircraft skidded during taxi after encountering black ice which resulted in aircraft impact with several runway edge lights.
Date: 202201
Location: ZZZ.Airport, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: APU Pneumatic System & Ducting
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Human-Machine Interface; Troubleshooting; Situational Awareness; Communication Breakdown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Human Factors; Aircraft; Incorrect / Not Installed / Unavailable Part; Procedure
Primary problem: Incorrect / Not Installed / Unavailable Part

Narrative: Aircraft X arrived t the gate with the clamp missing on keel beam APU duct pressure seal. After further inspection; I found that the clamp had slipped off AND WAS NOT MISSING. The aircraft was taken out of service because of the lengthy time required to correct this issue. This can lead to potential pressurization issues and leaks. There have been several other aircraft seen with the same issue.




Synopsis: Technician reported aircraft arrived at station with the keel Beam APU pressure duct seal clamp not installed. The aircraft was taken out of service for maintenance action.
Date: 201403
Local time of day: 0001-0600
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class D ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Engine Control
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: 30 minutes into flight at 6;500 feet; the engine began to run rough and started to cut out intermittently as if it were lacking fuel. I checked the gauge and I had full rich mixture and full throttle and ample fuel. I was losing altitude. I communicated via radio that the engine was not running right. I declared an emergency and was given clearance to land. I landed the airplane and taxied off the runway and as soon as I cleared the runway the engine died. My passenger and I safely exited the aircraft and greeted [the local] police who took my report and credentials. The airplane was towed to a transient parking spot. The next day I had the shop on the field inspect the airplane and found that a bolt connected to the mixture cable was loose. It was not properly controlling the mixture and the engine was in fact being affected by lack of fuel.




Synopsis: The pilot of a C182 experienced a loss of power and rough engine operation during cruise flight. An emergency was declared; followed by a successful landing. A loose mixture control fastener was determined to be causing a lack of fuel to the engine.