elihoole/asrs-aviation-reports huggingface dataset:
Date: 201509
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Rudder Control System
Component problem: Malfunctioning
Reporter organization: Contracted Service
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was called out to defer the L/H wing anti-ice valve per MEL on a CRJ-700. The work was completed but I apparently left the MEL manual paperwork in the area of the valve. Later the flight crew made a maintenance discrepancy that they felt binding in the rudder. The paperwork that was left in the valve area had worked its way to the flight control cables and was rubbing against the rudder cables.To prevent a recurrence I will double check that all paperwork has removed after the work has been complete.




Synopsis: A Maintenance Technician reported that maintenance paperwork had been left in the work area and caused a subsequent binding of the rudder cables.
Date: 201603
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Oxygen System/Crew
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Checking the Aircraft Maintenance Log (AML) I noticed the aircraft had been written up multiple times for crew oxygen leaking. Yesterday the Captain's oxygen mask and smoke goggle equipment box was removed and replaced from aircraft to repair a suspected oxygen leak. This morning when testing the crew oxygen mask communications microphone it failed to transmit anything spoken. Called maintenance and we troubleshot the issue. I had the First Officer double check his mask and I also checked the observer's mask and both of them worked fine. Contract maintenance came out and found that the repairs made the day prior were incomplete and the maintenance personnel failed to connect the cannon plug to backside of the emergency oxygen mask. Had we or previous crews had an emergency with smoke or fumes in the cockpit we would have been unable to establish communication with each other. Captain would not have been able to speak with ATC as microphone was not hooked up.Maintenance needs to follow maintenance manual procedures/diagrams when putting aircraft back together and a full functionality check of the entire affected system once repair is complete to ensure next crew has an airworthy and safe aircraft.




Synopsis: CRJ-900 Captain reported he noticed during preflight that his crew oxygen mask had been serviced improperly and he would not have been able to communicate using it.
Date: 201907
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Ground Personnel
When detected: Taxi
Result: Flight Crew Returned To Gate; General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I was the Lead on flight XXX. I noticed I had a dangerous good on my loading from the store department. Originally; I had loaded on Pit 5. Upon pushing the flight I realized I did not have the required bags around the dangerous good. I went in the ally way. I moved it from Pit 5 to 4. After the aircraft taxied out I was not able to close out the flight due to the fact that particular Airbus 320 had a netting system no dangerous goods in the nesting system. At that point I had contacted Operations to bring the plane back to the gate; which they did. I moved the dangerous good from Pit 4 to Pit 6 and also moved 5 bags from Pit 4 to 6 to have enough bags surrounded the dangerous good.




Synopsis: Air carrier Ramp Lead reported aircraft ground return to correct Hazmat cargo load error.
Date: 202010
Local time of day: 0001-0600
Location: FSD.Airport, SD
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp FSD
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Distraction
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Environment - Non Weather Related; Human Factors; Airport
Primary problem: Airport

Narrative: FSD ramp area lighting insufficient intensity creating dangerous shadows and making it difficult to see ramp to taxiway transition.




Synopsis: Air carrier Captain reported insufficient airport lighting in the taxiway and ramp area at FSD.
Date: 202108
Local time of day: 0601-1200
Location: SJU.Airport, PR
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower SJU
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Confusion; Distraction
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Air Traffic Control; Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented
Contributing factors: Chart Or Publication; Procedure; Human Factors
Primary problem: Human Factors

Narrative: Taxiing to Runway 8 at SJU; we were cleared to taxi and hold short at S1. I noticed the Captain wasn't going to make the turn at S1; so I prompted him; but it was too late and stopped just past the intersection. Tower called us and said that S intersection was closed; so there was no way for us to turn around and return to S1. Tower called a follow me ops vehicle and instructed us to follow him through S intersection; onto the runway and then taxi off at S2. We complied and returned for takeoff from S1. We missed complying with the taxi instructions; but there were no markings of the closed intersection; and the ATIS was unclear; stating only 'S intersection closed'; which seemed ambiguous since it didn't mention S at Runway 8 closed.




Synopsis: Air Carrier pilot reported unclear ATIS information and a lack of markings resulted in a taxiway incursion at SJU.
Date: 201712
Local time of day: 0601-1200
Location: SFO.Tower, CA
Light: Daylight
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operating under: Part 91
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: Tower SFO
Reporter organization: Government
Reporter function: Handoff / Assist
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Human-Machine Interface
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued New Clearance
Contributing factors: ATC Equipment / Nav Facility / Buildings; Airport
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: I was working Local Assist. Aircraft X was instructed to line up and wait on Runway 1R. When in position; the Local Controller attempted to reach Aircraft X on the frequency several times; but was unable. This has happened many times before with lower profile jets (smaller Citations; Lear Jets; Phenoms; etc). There is apparently a dead spot where the tower antennas do not reach low profile jets while they are in position on Runway 1R. The only way to reach them is to relay a message to them through another aircraft. I told the Local Controller about this and told them that they should tell an air carrier jet who was holding short of Runway 1R to instruct Aircraft X to move up a few feet to get out of the dead zone. We re-established communication with the jet and cleared it for takeoff. Tech Ops needs to find a solution so that the entirety of all runways are receiving radar coverage for all aircraft types. This problem should not persist as it could potentially lead to some very unsafe situations if; for instance; cancel takeoff clearance instructions are not heard.




Synopsis: SFO Tower Controller reported a radio 'dead spot' identified at the approach end of Runway 1R that continually affects lower profile jets when in position on the runway.
Date: 202002
Local time of day: 1201-1800
Location: FAI.Airport, AK
Flight conditions: IMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E FAI
ATC / advisory: TRACON FAI
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
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Automation Aircraft RA; Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: On descent into PAFA talking to FAI approach noticed TCAS traffic in a climb at our 11 o'clock moving to 12 o'clock position approximately 3-5 miles away. We were IMC; in the descent to 7000 ft. No traffic call of any sorts from Approach Control about the traffic. As the traffic closed in on us; I disconnected the autopilot and initiated a climb to avoid the traffic. About the same time; we received a TA followed immediately by a RA. Still no call from Approach Control. My FO (First Officer) called Approach Control to advise of our traffic conflict and that we were climbing to avoid. Multiple alarms were heard in the background of the Approach Controller's transmission when [the Controller] called back to command a climb clearance to us. We passed above the traffic by approximately 400 ft. We then cleared the traffic and descended back to 7000 ft. and landed uneventfully.




Synopsis: Air Carrier Captain reported an NMAC in IMC inbound to FAI.
Date: 202001
Local time of day: 0601-1200
Aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Hydraulic System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was in cruise at 9;500 ft. when both L and R HYD Flow lights started to flicker. I started descending and started heading toward ZZZ. I referenced the QRH running though the LEFT/RIGHT HYDRAULIC FLOW LIGHT ILLUMINATED checklist. Told ATC i was diverting to ZZZ. On the right midfield downwind I decided to put the gear down. With the gear handle down I only had the two main gear lights green with no nose indication. I referenced the LANDING GEAR WILL NOT EXTEND HYDRAULICALLY; trying the press to test and then trying to change the nose gear bulbs with no luck in showing a green indication. I blew the gear down per the QRH procedure; I heard a thump of the gear going down but only had an indication of the left main gear down (green) I continued the checklist by checking the gear warning horn and it did not sound. At this point I [requested priority handling] with ZZZ tower and requested the firetrucks. I referenced the QRH checklists landing with defective main and nose gears and told the tower I was ready for landing. I followed the checklists killed the engines and landed on the good wheel. All 3 gear were down and I stopped on the runway. HYD fluid was all over the right engine. I requested a bus for the 2 passengers and a tow back to the gate. I received clearance from on call duty manager before allowing them to tow the plane to the gate. Cause: HYD leak/Problem and Gear Indication problem.




Synopsis: Pilot reported a hydraulic system failure that resulted in a diversion.
Date: 201912
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Main Gear Tire
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Rejected Takeoff; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Rejected takeoff at approximately 110 kts after aircraft started shaking badly; [making a] loud noise and pulling to one side. Captain was Pilot Flying. First Officer called out blown tire as I was in the process of rejecting the takeoff. We remained on the runway with about 4;500 feet left. Rejected takeoff procedure followed; brake cooling on [weight and balance] completed; after aircraft was inspected and unable to be towed off runway. Passengers were deplaned by stairs into buses with assistance of fire department. Aircraft logbook was filled out and handed over to Maintenance. Cabin Crew and Passengers were given updates throughout the process and time it took to evaluate the aircraft and deplane them.


Second narrative: During takeoff at ZZZ; at 110 kts; the right main inboard tire failed; causing a loud bang and strong vibration. I called 'tire failure' and the Captain simultaneously decided to reject the takeoff. He executed the rejected takeoff procedure and worked to maintain centerline. I verified the correct procedure (it was correct) and notified Tower. We stopped on centerline with 4;000 feet remaining. Maintenance and Airfield Operations advised us that hydraulics were leaking and we couldn't taxi and an attempt to tow the aircraft failed due to a locked brake; the passengers were unloaded onto busses.


Synopsis: B737 flight crew reported a tire failure that resulted in a high speed rejected takeoff.
Date: 202109
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: DJI Air 2S
Operator: Recreational / Hobbyist (UAS)
Flight plan: None
Mission: Training
Flight phase: Cruise
Aircraft component: Transmitter (UAS)
Component problem: Malfunctioning
Reporter organization: Recreational / Hobbyist (UAS)
Reporter function: Person Manipulating Controls (UAS); Remote PIC (UAS)
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Equipment Issue
Detector: Person UAS Crew
When detected: In-flight
Result: Aircraft Lost Link (UAS); Flight Crew Landed As Precaution; Flight Crew Regained Aircraft Control
Contributing factors: Aircraft; Human Factors; Software and Automation
Primary problem: Ambiguous

Narrative: I was flying my drone over some woods when the controller screen went blank. The footage had been glitching all day. This is an ongoing issue with Smart Controllers and DJI Air 2S based on my research. I contacted the company and they have told me to try some things and blamed it on the software.

Callback: Reporter stated the smart controller has intermittent connectivity with the UAS. Partial lost links have occurred but reporter has always been able to regain control of the UAS.



Synopsis: Hobby UAS pilot had a controller malfunction while flying. Pilot landed UAS safely.
Date: 201510
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: SR20
Operator: FBO
Operating under: Part 91
Mission: Training
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Cylinder Head Temperature
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition

Narrative: Flight crew flew to Airport ZZZ without any issues. Landed and taxied back to take back off to return to Airport ZZZ1. ZZZ Ground issued clearance for return back to ZZZ1. Flight crew was on the ground for about 2 minutes. Flight crew took off Runway 9 at ZZZ. Pilot Under Instruction (PUI) flew runway heading up to 2;000. We were then cleared to ZZZ1 at 3;000. When the crew loaded the GPS and continued climbing we noticed the Cylinder Head Temperature (CHT) cylinder 5 had spiked. Instructor contacted [and advised] ATC which gave us a clearance turn to the airport and maintain 2;000. We then were swapped to Tower and cleared to land. CHT came back down when we started the descent to land. No further issues after landing. Returned aircraft to FBO ZZZ and shut down. Instructor checked the oil and found it to be normal after landing. Instructor took evasive action and [advised ATC] as pilot in command.




Synopsis: SR20 crew noticed high Cylinder Head Temperature (CHT) shortly after takeoff. Crew received clearance to return to airport. CHT indication returned to normal range prior to landing.
Date: 201303
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Light: Night
Aircraft: DC-10 30
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Electronic Flt Bag (EFB)
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: Flight Crew Returned To Clearance; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Briefing the departure procedure the crew missed the non-standard climb gradient to the 16;000 FT crossing restriction at the departure fix. However; the crossing restriction itself was entered in the FMS. As a result; the crew should have notified ATC that it was unable to comply with the climb gradient since the requirement was 500 FPM and Econ Climb only yielded 493 FPM; or use max climb speed; which would have yielded a rate of climb in excess of that which was required. The crew departed and made the restriction; but by maintaining a slower than normal climb speed.Transitioning to the Commercial Chart Company's format seemed to be an issue in this case since the pages in normal mode are illegible; causing the crew to have to zoom in. The Commercial Chart only permits one level of zoom; so the page goes from too small to too big; causing the crew to have to hunt around the page for information. The other issue that must be accommodated with the Commercial Chart Company is that the pertinent information is so cluttered that it gets lost; versus the other Commercial Charts which presented only that information for departure from the particular operational runway. These are factors that the crew will have to deal with and adjust to over time with the use of Commercial Chart Company's EFB.




Synopsis: First Officer chronicles the difficulty deciphering EFB chart information and text in both normal and zoom mode.
Date: 201812
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: 10
Light: Daylight
Aircraft: TBM 900 / TBM 930
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Climb
Airspace: Class E ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Captain
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Human Factors; Airspace Structure
Primary problem: Human Factors

Narrative: Controller stated per our conversation that I showed .5 miles south of course while intercepting the outbound course to ZZZZZ intersection. The Controller issued a low altitude alert due to the MEA in that area. The Controller also stated he could see me in the turn outbound to ZZZZZ when the alert was issued and that other than the MEA there was no conflict with other aircraft or terrain. I was VMC until clear of all terrain and there were no TAWS alerts received.




Synopsis: TBM pilot reported ATC identified an off course and low altitude situation.