elihoole/asrs-aviation-reports huggingface dataset:
Date: 201504
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Second aircraft: EMB ERJ 170/175 ER/LR
Aircraft component: AC Generator/Alternator
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Situational Awareness; Time Pressure; Workload; Distraction
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Aircraft X; an ERJ-170; had a failed Generator Input/Output Module-2 card (GEN I/O 2) and needed to leave soon for a flight to a larger Maintenance Base for scheduled maintenance that night. We didn't have a card here to replace it with; but had Aircraft-Y (ACFT-Y) with the same type of card. So I took ACFT-Y's GEN I/O 2 card out; noting the arrow was facing UP. Took it to Aircraft-X (ACFT-X) to replace it (with the arrow facing Up; the way I removed it) with the canned (cannibalized) [card] from ACFT-Y. Loaded the card [into Aircraft-X] and ran the Ops Check; everything tested good at the time. We went AOG for a new card for ACFT-Y.  Once we received it; I installed the new card in ACFT-Y with the arrow; face Up; the way I removed it. Loaded the card and ran the Ops Check and everything passed. We had the Aircraft Maintenance Manual (AMM) with us to locate the card slot number in the Modular Avionics Unit (MAU2); but in the rush of getting the card out [of Aircraft-Y] and loaded into our Maintenance Tracking and Parts computer program to be [considered] Serviceable to be installed on ACFT-X; we did not notice the step annotating the arrow [on the card] should be in the DOWN position. With both Aircraft passing the Operational Checks we went about thinking it was correct until there was an error a few days later that it was then brought to my attention it was installed upside down on both aircraft.[Contributor] Wanting to make sure the aircraft was fixed before the flight crew timed out; to get it to a Base for its scheduled workload; the task was done without full notice to the AMM stating the direction of the arrows. [Recommend] Be sure to fully read all steps of the AMM. Do not believe [assume] that the current installation of a part is the correct configuration for it to be in. Cannibalize part for another aircraft. Ramp. Gate.




Synopsis: A Line Aircraft Maintenance Technician (AMT) was informed he had installed a cannibalized Generator Input/Output module-2 card (GEN I/O-2) upside down into the Modular Avionics Unit-2 (MAU2) on an outbound ERJ-170 aircraft. Technician noted that even though both cards were removed and reinstalled with the arrows facing up; instead of down; they still passed the AMM Operational Checks.
Date: 201707
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Skylark 175
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Parked
Aircraft component: Powerplant Mounting
Component problem: Design; Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer; Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft was modified with an STC engine change. During engine change the engine mount; between engine and firewall; was modified which was outside the STC specification. Further; exhaust system was installed incorrectly thus partially separating from engine cylinders in flight.




Synopsis: Cessna 175 pilot reported that the aircraft was removed from service due to maintenance issues that were not in compliance with FARs.
Date: 201606
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Drinkable/Waste Water Syst
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Manuals; Procedure; Company Policy
Primary problem: Procedure

Narrative: Person X informed me that he had performed a 'maintenance only' test on each of the lavatory hot water systems and determined that all were malfunctioned. When I inquired further as to how he determined the operational status of the water system he explained to me a mechanic had shown him how to initiate a self test on each lav by opening the panel below the sink and turning some switches; then look for a light [to] illuminate. After conferencing with dispatch and maintenance control we were all in agreement that an illegal and unauthorized tampering of each lav's electrical component had occurred; and each had to be inspected by maintenance to confirm switches and breakers etc were in the correct position. A log book entry was made.Person X performed an illegal and unauthorized test of the lavatory hot water system. I attempted to explain to him the breach of safety that had occurred. I do not believe I was able to convey a satisfactory answer to him on why he should discontinue this practice.   I do not believe this practice is wide spread. I do believe a conference with his immediate supervisor is appropriate.




Synopsis: An air carrier Mechanic reported non-maintenance personnel performed a 'maintenance only' test on each of the lavatory hot water systems and determined that all were malfunctioned.
Date: 201910
Local time of day: 1801-2400
Light: Night
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were filed for the ZZZ RNAV SID transition but cleared on the ZZZ1 Departure. Per the SID we turned southwest and were switched to departure at 1;000 ft. where the initial instructions were confusing to Pilot Monitoring. We leveled at 3;000 ft. were instructed to climb to 10;000 ft.; but the turn direction (left) and heading 080 were confusing to Pilot Monitoring; who spun the heading right instead of left resulting in incorrect FD guidance and preventing autopilot engagement as a means to task shed. The Pilot Monitoring was unable to understand the clearance direct to ZZZZZ; resulting in several transmissions to resolve the spelling of the fix. It quickly became evident to me that Approach and later Center (switched at 10;000 ft.) believed we were on the ZZZ RNAV SID; but that was not our clearance. Because we were not cleared on the ZZZ SID; we did not brief the ZZZ SID; and lack of familiarity with the fixes ZZZZZ and later ZZZZZ1 coupled with regional accents made it difficult for the Pilot Monitoring to manage radio communications and FMS entries.We were filed for the ZZZ SID but cleared on the ZZZ1 Departure. ZZZ departure and center expected us on the ZZZ with its unusual routing (take off south; turn southwest; then turn back east for climb; then south; and finally again southwest toward destination) and multiple fixes. Clear flights on the ZZZ SID if departure and center are going to reference multiple points on the ZZZ SID during the climb through ZZZ airspace.




Synopsis: B767 Flight Crew reported they were cleared via a departure different from what was expected and filed.
Date: 202003
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Troubleshooting; Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Ambiguous

Narrative: With the spread of the COVID-19 virus still spreading throughout the world; we here at Company need to do our part to help stop the spread of the virus to each other; our families; friends and the communities we live in. After looking at all the time clock areas I noticed that there are no hand sanitizing stations there. We hourly employees have to use our hands to clock both in and out and that's just another potential point of contact for the spread of the virus and not just at our time clocks but also point of entry to the sterile work areas including the ramp. Today when I asked for a hand sanitizing wipe packet; the person behind the equipment counter said they were all out and they didn't have any alcohol wipes either.




Synopsis: Ground employee reported the lack of sanitizing agents especially in the clock in/out areas.
Date: 202011
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Procedure
Primary problem: Airport

Narrative: While in the traffic pattern we turned to a left crosswind and encountered a traffic conflict with another aircraft (C172) who was downwind. We did not receive any kind of advisory or instruction(s) from ATC. Both pilots (us and the other aircraft) took proper evasive action. Contributing to the incident; the controller was working 2 runways in a very busy environment. In addition; the other aircraft appeared to be in a longer traffic pattern than normal.




Synopsis: C182 Pilot reported a NMAC on crosswind at controlled airport resulted in evasive action.
Date: 202111
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Situational Awareness; Confusion
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I had just landed on Runway XX and exited on the ground via taxiway Kilo. I was instructed to take taxiway Kilo to Foxtrot to the ramp for parking and disembarking. However; I made a mistake and turned right onto Bravo from Kilo rather than crossing Bravo before turning right to stay on Kilo. About the same time I noticed my error ZZZ Tower had contacted me and updated my instructions to taxi via Bravo; Alpha; Hotel to the ramp; which I successfully completed without further issues. Luckily I was the only aircraft maneuvering on the ground at the time and this did not endanger or impede any other aircraft or persons at the facility. In the future I need to take a few extra moments to verify my instructions and the airport diagrams to prevent any further deviations that could result in damages or injury by going the wrong way.

Callback: The reporter had no additional information to note.



Synopsis: PA-28 student pilot made a wrong turn on a taxiway after landing. ATC issued a new clearance and the pilot continued their taxi to parking.
Date: 201711
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Pitot-Static System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Speed All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Procedure; Aircraft
Primary problem: Ambiguous

Narrative: No violation of FARS but I want to document the event for future aviation safety. Shortly after takeoff we had IAS caution and ALT caution on both PFDs (Primary Flight Displays). Also had EFIS COMP MON and MACH TRIM caution messages. I was flying and my Captain pulled out the QRH for the two caution messages. However; our airspeeds and altitudes did not match and we were unsure of both airspeed and altitude. We [advised ATC] and asked for vectors to figure out the problem. We asked ATC what they showed for our airspeed and determined that my airspeed indicator was incorrect (I was showing 250 knots while Captain's PFD was showing 310) and my Captain's airspeed indicator was correct. We then asked ATC what they had for our altitude and they said 8000 ft. I was displaying 8000 ft while my Captain was showing 11;000 ft. So; my airspeed was incorrect but my altitude was correct while my Captain's airspeed was correct but altitude was incorrect. Also; our TCAS was not working. While we were trying to solve the problem a plane flew right by us with no indication from TCAS nor from ATC. I had to pull the power quickly to avoid the plane. We know something drastically went wrong with our pitot-static system or was wrong before we even departed. We first flew the plane out of maintenance for a 'bird strike' that maintenance signed off but Tower did not think they did. Perhaps it was damage from the bird strike or debris flew in the tube or it was loose or who knows what. More thorough maintenance. Maintenance should be in house. This event could have been a lot worse than it was.




Synopsis: CRJ-700 First Officer reported erroneous airspeed and altitude indications on both pilot's primary flight displays.
Date: 201710
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Operating under: Part 91
Mission: Personal
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Fuel Crossfeed
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Human factors: Situational Awareness; Time Pressure; Troubleshooting
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 Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I failed to switch fuel tanks properly and ran the left fuel tank dry causing the engine to lose power. I informed ATC that I had an [issue] and located [a diversion] airport nearly under me. Over the airport spiraling down I had time to determine that I had run the tank dry and switched to the other tank with over 20 gallons of fuel left and the engine restarted normally. I continued to my destination.I had stared out with full fuel; 90 gallons; switched tanks at .5; 1.5; 2.5 hours after take off. After that time I forgot to do the tank switch at 3.5 hours and the left tank ran dry at 4.0 hours. I lost about 2500 feet before I restarted the engine. I quickly determined I could reach [a diversion] airport with no problems and I was actually trying to lose altitude to set up for a dead stick landing at the airport. I should have set up for best glide and I should have run the emergency checklist earlier to determine the problem. Had I been at a lower altitude the problem would have been more serious.I almost always fly distances of less than an hour so fuel management isn't normally an issue because starting on the tank with the most fuel is sufficient for my trips. This trip was a longer; about 4.3 hours; I was out of practice dealing with fuel management issues until my normal GUMP check approaching the destination runway.




Synopsis: A single engine Cessna pilot reported the loss of engine power due to fuel crossfeed mismanagement. While descending to accomplish a landing; he successfully reconfigured the fuel system; restarted the engine; and continued on to his destination.
Date: 201907
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Commercial
Human factors: Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Other landing roll
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: After touchdown; the aircraft failed to maintain directional control and veered to the right. The aircraft left the runway and dragged the left wing on the grass.




Synopsis: Light aircraft pilot reported loss of directional control after touchdown resulted in wing tip contact with the grass.
Date: 202002
Local time of day: 1201-1800
Location: MIA.Tower, FL
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Fractional
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B MIA
ATC / advisory: Tower MIA
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Fractional
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During final Visual Approach to RWY 26R at MIA; at 1;000 FT MSL AND 3 NM from the RWY; we saw a small black drone static from our left side; no evasive action was needed. We alerted the tower about the sighting and [the] controller mentioned that he would gather some more info as soon as we landed. Indeed; he asked us about the size; color; and if any evasive action was taken. We provided the info and mentioned no evasive action was taken. Controller advised the traffic behind us about the drone.




Synopsis: Pilot reported seeing a small drone on the left side of the aircraft at 1;000 ft MSL and 3 NM from the runway while the flight was on final approach.
Date: 201905
Local time of day: 1801-2400
Location: FCM.Tower, MN
Flight conditions: VMC
Light: Daylight
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class D FCM
ATC / advisory: Tower FCM
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Reporter organization: Government
Reporter function: Local; Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Other / Unknown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure; Airport
Primary problem: Airport

Narrative: I was working Local Control and Ground Control. I had Aircraft X cleared  to land Runway 28L and an Aircraft Y taxing out to Runway 36 for departure holding short of Runway 28L for Aircraft X to land. There was a phone call on the land line around the same time from the police department regarding searching for a missing person. The Aircraft X pilot on short; short final asked if he was lined up for the correct runway. Due to our location of the Tower; we cannot see. I sent Aircraft X around. Had he not questioned this he would have landed on an incorrect; shorter; runway but what could have been worse was the Aircraft Y taxing out crossing that runway at the same time he questioned the runway. I would have never questioned the runway he was lined up for had it not been the pilot had not said something. We need a tower in a place where we can see the runways and one that gives the controllers an opportunity to save this situation from happening. Relocate the control tower in a better place.




Synopsis: FCM Tower Controller reported they instructed an aircraft lined up with the wrong runway to go around when there was traffic crossing the same runway.