elihoole/asrs-aviation-reports huggingface dataset:
Date: 201406
Local time of day: 1201-1800
Location: MKG.Airport, MI
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Flight plan: IFR
Flight phase: Parked
ATC / advisory: Tower MKG
Reporter organization: Government
Reporter function: Approach; Instructor
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Provided Assistance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: During the relief briefing I failed to brief the relieving Controller that Aircraft X had made an instrument approach to LWA and that MKG Approach was still waiting for his cancellation. 15 Minutes later South Bend Approach called asking about the block that we had established over LWA. My relief said that they would find out about it; and a few minutes later South Bend called to inform us that Flight Service had called them with the cancellation.I will be more vigilant about aircraft that drop off the scope and still require my attention. I was training at the time; and the scope setup that the trainee uses is different than mine. On my scope setup; I have the dropped aircraft tags appear right over the LWA and BIV airports so that I am reminded that I need to get their cancellations. I also put the strip in a spot at an angle in the bay so that I remember to take care of it; or brief the status. Since these things are not done by everyone; I missed the information and it was not passed to the next controller.




Synopsis: MKG Controller reports that he forgot to let a relieving Controller know that an aircraft had just landed at an airport in their jurisdiction; but did not cancel IFR.  Relieving Controller did not know about this until quired by another Controller as to why the airport airspace was blocked.
Date: 202008
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Weather elements / visibility: Rain; 4
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Climb
ATC / advisory: TRACON ZZZ
Aircraft component: Flight Dynamics Navigation and Safety
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument
Human factors: Troubleshooting
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Equipment Problem Dissipated; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Climbing out in IFR conditions I lost GPS signal to my KNS 750 which skewed my G5 heading. I was given a heading and had to check my magnetic compass to comply. My GPS signal came back after about 5 min. I don't believe their was any separation issues. I landed and called my mechanic and told him what happened. He thinks with the RAIM (Receiver Autonomous Integrity Monitoring) that we have to ground the control surfaces. He has only heard of this one time before. I told him that I will not take that plane up again in IFR conditions without fully going through the panel.




Synopsis: C182 pilot reported temporary loss of GPS Navigation system during IFR flight.
Date: 201206
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Oil Cooler
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Human Factors

Narrative: I Removed and Replaced (R/R) the Fuel Flow Transmitter on the Left-Hand Engine (# 1 Engine). This was due to an Engineering request that it be replaced since there was a history of high fuel consumption. When the Task was completed; I performed an Engine Run to [do] Operational/Leak Check of the engine. No faults were noted. The aircraft flew ZZZ to ZZZ1 with no faults. Upon landing on the return ZZZ1-ZZZ trip; when the Thrust Reversers were deployed; the Left-Hand Engine shut down. When the aircraft was inspected; it was discovered the gasket for the [Fuel] 'In' tube at the Fuel/Oil Cooler had failed. I had replaced the same gasket the night before as part of the Fuel Flow (F/F) Transmitter replacement. At this time I am not aware if this is the result of a gasket failure or procedural error on my part.

Callback: Reporter stated the Fuel/Oil Cooler is mounted on the right side of the combustion case on GE CF6-8 engines. He had to remove a fuel line (tube) that ran from the Fuel Flow (F/F) Transmitter to the Fuel/Oil Cooler in order to replace the F/F Transmitter. The metal gasket he installed between the 'In' tube coupling flange on the fuel line and the Fuel/Oil Cooler housing flange has an 'O-Ring' type seal on both sides of the gasket. When Maintenance opened-up the CF6 Engine cowling after the engine had shutdown on landing; a small amount of fuel was noticed on the engine. But; when the Engine Leak Check Run was performed; fuel was spraying everywhere.Reporter stated a piece of the 'O-Ring' seal was missing from the metal gasket; but he doesn't know if one; or both seals were cut; or missing a seal section when he installed the metal gasket. The B767-300 did fly two legs without any known problems prior to the shut down. He noted that having the engine shut down on landing was a better situation than having the seal fail on Takeoff with a potential engine fire. A new gasket was installed; Engine Run accomplished; no further leaks.



Synopsis: A Line Mechanic reports the left engine on a company B767-300 aircraft had shutdown on landing when the thrust reversers were deployed. A metal gasket he had installed between the fuel/oil cooler housing and the fuel 'In' tube connection to the fuel/oil cooler had failed.
Date: 201305
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Weather elements / visibility: 10
Aircraft: King Air C90 E90
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: AC Generation
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: On the initial climb I noticed fuel gauges showed lower than during the preflight; then I noticed the left generator inoperative light on that was followed by flickering of the PFD and MFD displays on both pilot and co-pilot sides.  I informed the Co-Pilot to tell ATC that we were heading back and to lower the landing gear.  ATC asked if we wanted to declare an emergency; we declined.  When the Co-Pilot attempted to lower the gear the panel lost all electrical power and communication was lost.  I shut the master and generators off and reset them back on.  We regained electrical power out of both generators.  We advised ATC that we had regained electrical power and they asked our intentions.  We advised them that we would continue to our destination.  ATC gave us vectors to the north and we started the turn except that PFD's were still getting aligned and magnetic compass was spinning.  Seconds later we regained heading information in our PFD's and resumed the flight.




Synopsis: King Air Captain experiences a left generator inoperative light on; that was followed by flickering of the PFD and MFD displays on both pilot and co-pilot sides.  The Captain instructs the First Officer to lower the landing gear which apparently kills the entire electrical system.  The electrical system is successfully reset and flight continues to destination.
Date: 202101
Aircraft: Commercial Fixed Wing
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Airspace: Class A ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: FA B and FA D repeatedly requested all passengers in the same party to lift and secure face coverings. Passengers would only cover up when flight attendants walked by.




Synopsis: Flight Attendant reported a group of passengers were no compliant with face mask policy during flight.
Date: 201306
Local time of day: 0601-1200
Location: ZZZ.Tower, US
Flight conditions: VMC
Light: Daylight
Aircraft: B717 (Formerly MD-95)
Operator: Air Carrier
Flight plan: IFR
Mission: Test Flight / Demonstration
Flight phase: Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Compressor
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were performing a Maintenance flight; and during the initial climb after takeoff passing through 1;000 feet; we started a right turn to a heading of 270. As we started our right turn the engine developed a compressor stall.  We leveled off; declared an emergency with the Tower; and requested delay vectors to run the checklist.  After completing the required QRH checklist; we requested the longest available runway; we accomplished the climb; in-range; and landing checklists; returning to our departure airport.  We operated the engine at reduced power following the QRH checklist.  We experienced vibrations followed by loud bangs; with a delay the EAD finally posted a R ENG COMP STALL followed by ENG R SYS FAIL MSG. The landing was uneventful with the fire trucks standing by; after we had requested an inspection of the right engine. The fire truck reported no visible damage. The taxi in was normal with no additional problems with only the R ENG COMP STALL msg.




Synopsis: When climbing through 1;000 feet during a maintenance test flight; the right engine of a B717-200 developed a compressor stall. The crew leveled; reduced power on the malfunctioning engine; declared an emergency; and returned to land.
Date: 202102
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: Caravan Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb; Climb
Airspace: Class D ZZZ1; Class E ZZZ
ATC / advisory: Tower ZZZ1
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Workload; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Strong burning smell like hot wires shortly after departure. Since bleed air (heater) was on; my first step was to turn bleed air off assuming that is likely engine fumes. The switch would not turn off air; and hot air continued to enter and smell persisted. Thermostat control also would not change the air flow. Since the smell was abnormal and stronger than a common smell of TKS entering the engine (the TKS system was not used); I elected to return to ZZZ which had airport fire facilities and was only a few minutes away. In the event that were was a fire or something was about to catch fire; I elected to request priority handling and executed the in cabin fire checklist. Upon landing at ZZZ; no further indication of fire was present and I meet the airport fire on the ramp. Their investigation did not find anything that was or had been burning. Aircraft was secured on the ramp for inspection by a mechanic.




Synopsis: C-208 Captain reported a burning odor during initial climb resulting in a return to the departure airport.
Date: 202101
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Airspeed Indicator
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: As pilot monitoring; first officer was receiving a Line Check for a requalification; due to a lapse in currency due to COVID-19 pandemic.During the takeoff roll; I checked all airspeed indications on both sides of the cockpit per SOP.  At 100 knots entering the high-speed regime; I observed my airspeed indicator (Captain's); was now reading zero airspeed and there was an orange flag.  I realized the airspeed indicator had failed and I called out the reject and took positive control of the aircraft.The auto brakes activated in the RTO function and we cleared the runway and followed SOPs.The aircraft [was taken] out of service for further inspections.  There were no injuries to either crew or passengers and no damage to the aircraft.


Second narrative: While departing on the takeoff roll; the Captain initiated a rejected takeoff.  Once the rejected takeoff was initiated; I radioed Tower; advised of the reject and asked for vehicles due to possible hot brake conditions. I then addressed the passengers and asked them to remain seated. The rejected takeoff was initiated above 85 kts (because the RTO brakes engaged automatically) but prior to the 100 kt callout.  The Captain appropriately exited the runway and advised me that he had a witnessed a faulty airspeed indicator display which is why he elected to reject the takeoff.Once clear of the runway; and stopped on the taxiway; we initiated the Rejected Takeoff QRH/QRC procedures.  Once complete; we made proper notifications to the cabin crew; ATC; dispatch and company.The entire event was handled very professionally and efficiently by all involved.Once at the gate; the passengers were all booked on a later flight to ZZZ1 [airport]; the aircraft was removed from service; and the airspeed indicator was replaced.  The Captain and I operated the same aircraft back to ZZZ1 the next morning without issue.


Synopsis: Air carrier Captain reported the airspeed indicator failed on the Captain's side during takeoff roll resulting in a rejected takeoff.
Date: 201602
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Main Gear Tire
Reporter organization: Air Carrier
Reporter function: Technician
Human factors: Confusion; Workload; Time Pressure
Second reporter function: Technician
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Taxi
Contributing factors: Human Factors; Incorrect / Not Installed / Unavailable Part; Procedure
Primary problem: Incorrect / Not Installed / Unavailable Part

Narrative: We got a call for a Main Landing Gear tire showing cord. We arrived as the passengers were starting to board. My partner started jacking the plane & I serviced the tire. We removed the old tire; swapped them out; and everything seemed to fit fine. We loaded up and went to the parts department to get another tire. It was then that we discovered our mistake and immediately called our lead to try to stop the plane; but it was too late.We went straight over to parts to swap out tires; entered our info on the computer; and realized what had happened.If I knew exactly why; this never would have happened. As we were leaving; another mechanic was using our truck to service a CRJ 900 tire. We arrived at the CRJ 700; feeling a little pressure to get it done quickly; as the passengers were boarding as we got there. I serviced a tire; we swapped it out; and got out of the rampers' way so the plane could be pushed back. The only difference in the two tires is the shoulder width at the hub; and we didn't catch it. The lead on duty was immediately contacted; to see if we could keep the plane from taking off; but it was too late.I need to be more vigilant in learning the new company policies on the color coded caps on the tires for identification purposes; and double check that I'm on the correct CRJ in the future.


Second narrative: This event happened on the ramp during routine line maintenance. A main landing gear tire assembly needed changed on a CRJ 700. A CRJ 900 main landing gear tire assembly was installed on the aircraft. Once we had finished changing the tire we were returning it to our stores department; when it occurred to me that we had used a CRJ 900 tire assembly.We arrived at the aircraft inspected the tire determined it needed changed so I began jacking the aircraft and then proceeded to remove the tire assembly while I was doing this my partner was inflating the new tire assembly in our work vehicle and brought it out to the aircraft. Then we both proceeded to install the new CRJ900 tire assembly on the aircraft; which fits perfectly so no suspicion was raised. Once we realized what had happened we immediately notified the supervisor in charge at the time. Be more vigilant of the CRJ 700 and CRJ 900 tires because they are very similar.


Synopsis: Maintenance installed an incorrect tire on a CRJ-900 aircraft.
Date: 202008
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty); Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: Guest noted with vented mask enroute. Was advised of the policy change which prevents those vented masks. She indicated she was a doctor and was explaining the venting technology. I apologized and referred to the policy. If the station catches these prior it would reduce the in-flight workload.




Synopsis: Flight attendant reported a passenger was wearing a vented face mask which is not in compliance with policy.
Date: 202007
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Airspace: Class B ZZZ
Aircraft component: Fuel System
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Situational Awareness; Distraction; Workload
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors; Aircraft; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: I arrived at the gate for my flight. I noticed that there were numerous items in the logbook. These items required extensive review and actions that needed to be achieved. These items distracted me from my normal preflight sequence. As the Captain returned to the flight deck; we both went over the MEL items. He thoroughly reviewed the logbook and signed it. As I am very new on the plane with only 55 hours in the last 6 months; I concentrated on my expanded checklist as well as the aircraft internal checklist to accomplish the preflight. It was at this time I must have over looked the new entry 'FUEL DOOR CYCLE FORM REC.'Cause - There were multiple write ups [and a] new [fuel door] procedure.




Synopsis: Air carrier First Officer reported missing a logbook entry involving a new procedure. Lack of flying was cited as a contributing factor.
Date: 201809
Local time of day: 1201-1800
Location: SJC.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C SJC
ATC / advisory: TRACON NCT
Second aircraft: Bonanza 33
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On the Razzr4 arrival and cleared for the ILS 30L; as we were nearly turning onto final a Bonanza aircraft passed about 200-300 feet below and about 500 feet laterally under our left wing. There was no TCAS warning and I asked NorCal approach about the Bonanza; he replied that there was no transponder information but that there was only primary painted information.




Synopsis: A320 Captain reported a near midair collision encounter on final approach.