elihoole/asrs-aviation-reports huggingface dataset:
Date: 202006
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
Reporter organization: Contracted Service
Reporter function: Lead Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Confusion; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors; Environment - Non Weather Related; Company Policy
Primary problem: Human Factors

Narrative: I arrived at the gate for the meet and greet. I see the FO outside during his walk around and ask him if the airplane is fine as far as maintenance goes. He replied to me everything is fine and handed me a box of light bulbs he found underneath the aircraft. We walked together towards the aircraft. I entered the aircraft with my face mask on and entered the flight deck. The pilot then began shouting get out! I walked out; I asked the Flight Attendant is everything okay is he always like that? So I went back to the flight deck to retrieve the logbook without disturbing the pilot I was met with more yelling and shouting. I walked off to the back of the airplane with the logbook and checked if everything was okay and went to return the logbook where he began shouting get off of my airplane. I responded to him and said during maintenance it is the Mechanic's aircraft. I then walked off the airplane to call Maintenance Control to inform them of the disgruntled pilot. He followed me yelling; then went and locked himself in the cockpit. I told the Maintenance Controller 'You know if I look hard enough I can find a reason to ground the aircraft; but I'm not going to do that' He responded 'Yea; I agree we don't want to do that. Let me call Dispatch and Operations to see what's going on with the pilot.' The pilot then comes out of the airplane yelling and gets closer to me aggressively I responded in a professional manner and told: 'I could ground the aircraft but I'm not going to do that.' He then started yelling 'Then do it a big shot I'm going to get you fired.'Maintenance Controller called me back and said 'The pilot had already been very upset because 3 passengers didn't want to wear masks because of medical reasons and that put him in a very bad mood and he let it out on you.'




Synopsis: Technician reported a Captain was confrontational when he entered the flight deck.  Reportedly; the Captain had dealt with passengers not wanting to wear their COVID-19 masks.
Date: 202009
Local time of day: 0601-1200
Location: BOS.Airport, MA
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Chart Or Publication
Primary problem: Chart Or Publication

Narrative: The verbiage for the BOS PATSS 5 Departure for Runways 22L and 22R needs to modified to be less ambiguous to indicate that the FOXXX intersection is not part of the procedure for those runways.  The departure verbiage reads 'Climb heading 215 to intercept course (139 for 22L and 143 for 22R) to TJAYY do not exceed 210 knots until 520; then on depicted route to PATSS.'  When you look at the depicted route; the track from TJAYY to BRRRO is 091 with FOXXX between TJAYY on a direct line between TJAYY and BRRRO.  The diagram says that BRRRO is '4.6 from FOXXX' and '7.3 from TJAYY.'




Synopsis: Air Carrier Captain reported written dialog and depiction on chart do not agree.
Date: 202011
Local time of day: 0601-1200
Location: HOU.Airport, TX
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower HOU
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Human factors: Communication Breakdown; Confusion; Distraction; Workload
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Staffing; Company Policy; Human Factors; Procedure
Primary problem: Staffing

Narrative: We struggled to even get in a pushback call on Hobby Tower frequency. It was busy with high volume takeoff and landing and ground movements. We had briefed a taxi out from Gate to Runway 4. Tower and Ground were combined. The airport was using Runway 4 for takeoff and landing. Our first instructions from a very busy Tower Controller were unexpected. Tower said taxi via [Taxiway] Z; hold short [Taxiway] D. We had no way to ask for clarification. The frequency was very congested. Our role seemed to be to clear the alley to allow inbound company aircraft. The pace that the tower controller was speaking was impressive and very busy. Other Company seemed to be confused on the radio along with our crew. The pace was something you hear on LGA Ground frequency.We were issued further taxi instructions to follow Company to Runway 4. We verified our crossing clearances across [Runway] 13L and R. We discussed that the controller was in the Yellow. We used extra vigilance during this crowded taxi out to Runway 4. The pace never relented for the controller. He was doing a great job. But the situation was excessive for a routine departure out of our always bustling Hobby airport. It came as no surprise to us that we were cleared for takeoff on Runway 4; even though we were #2 in the lineup. We instantly questioned this; and our clearance was canceled. This seemed like a minor error to us; but it was confirmation that the professional controller was indeed in the Yellow. We departed minutes later without incident.Staff this busy airport with the correct amount of controllers. Loading up flight crews in this critical phase of flight over weak staffing is hazardous. I'm not sure if the guy was alone up there. He was really doing a great job. We know as crews; when the controllers are overloaded; we try to not make the situation worse with fumbled radio calls. The airport was operating in the Yellow; any small non-normal from an aircraft on the frequency could have made things go bad very quickly. We could have waited to move from our pushback into the alley until the radio calmed down




Synopsis: An Air Carrier pilot reported the tower controller was overloaded with traffic while working Local and Ground Control combined when they were cleared for takeoff even though they were number two in the departure lineup. The pilot stated this airport needs to be staffed with more controllers.;
Date: 201701
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Air Traffic Control; 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 Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: When landing gear was retracted after takeoff; the unlocked warning light illuminated. The landing gear was extended; and all three landing gear indicated down and locked. The landing gear was again retracted with the same unlocked indication. The landing gear was again extended where it remained for the duration of the flight. Three down and locked was again indicated. Tower was advised; as was departure control. A fly-by the tower was requested to see if any abnormality could be detected. The result was that the nose gear appeared to be cocked to one side. I requested radar vectors to burn off fuel. While orbiting we looked at the checklist for any pertinent guidance. There wasn't any specific procedure for this situation; other than a possible emergency evacuation. The crew discussed the possibility of the nose gear turning to a 90 degree position; or possibly staying in an offset position resulting in a turn off the side of the runway. The plan was therefore to lighten the aircraft by burning off three thousand pounds of fuel which would lower our landing speed; hold the nose off the ground with the elevator; and the use of reverse thrust; thus lowering the ground speed to the greatest extent possible before nose gear touchdown. After burning off three thousand pounds of fuel; and securing any loose objects in the cockpit; clearance to land was requested. A normal approach and touchdown was executed; except that the nose was held off with the elevator and the use of reverse thrust. When the nose gear finally touched down; there was a mild shimmy; and the aircraft proceeded straight down the runway. We were able to taxi to the ramp; and secure the aircraft. The tower informed us that the nose gear centered itself when it touched down. There was no damage to the aircraft.




Synopsis: CE-560XL Captain reported observing a gear unlocked warning light on takeoff. After flying by the Tower to visually confirm the problem; it was determined that the nosewheel was stuck sideways. The nosewheel straightened out during an uneventful landing.
Date: 202009
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Time Pressure; Communication Breakdown; Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Company Policy
Primary problem: Company Policy

Narrative: Upon arrival in ZZZ on Flight AB; fleet wanted to immediately board the aircraft without regard to social distancing. I at 1st asked them to wait and then motioned them on once there was an appropriate gap that allowed proper social distancing. Fleet wrote this up as they want to board immediately. My Supervisor sent me information advising that they need to get on immediately. This does not address the safety of our employees and guests by maintaining appropriate social distancing.




Synopsis: Flight Attendant reported boarding and deplaning issues related to social distancing concerns.
Date: 202112
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Gulfstream IV / G350 / G450
Operator: Air Carrier
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Flap Control (Trailing & Leading Edge)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On departure out of ZZZ; at 400 feet and adequate speed I as Captain and Pilot Flying called for flaps to be selected up. Everything was normal and passing through a few thousand feet around 200 knots the auto-throttles disengaged prompting me to search for a cause. At that moment I saw the flap handle was selected up and the flap/stab gauge was indicating that the flaps were still at 10 degrees. Following what I saw; we got a message in our FMS stating 'Flap input invalid'. I then prompted the First Officer to request a level off which was 13;000 feet and we kept the speed within flaps 10 limitations. I called for the 'Flaps fail to move/ Flaps lock up' checklist per the Gulfstream QRH. We then requested a holding pattern at ZZZZZ and a lower altitude. We began to troubleshoot while holding at ZZZZZ at 5;000 feet and 200 knots. That checklist didn't change anything so we elected to try the 'Flaps Alternate' Checklist per the Gulfstream QRH. Again the flaps stayed at 10. We then found that the flaps would move down beyond 10 but not back up to zero. We held at ZZZZZ long enough to get the plane below its max certified landing weight. We ran the appropriate checklists. ZZZ Tower [advised] for us; we landed in a normal configuration as the flaps did move to full. We landed on the longest possible runway at ZZZ.




Synopsis: G-IV Captain reported flap control malfunction during departure climb resulted in a return to departure airport and normal configuration landing.
Date: 201206
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: King Air C90 E90
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pressurization System
Component problem: Failed
Reporter organization: Corporate
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Diverted; Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In a normal climb; explosive loss of cabin pressure occurred between 16;000 to 18;000 FT MSL. I initiated an emergency descent; informed the Center; and I leveled at 10;000 FT MSL. I diverted the flight to ZZZ for maintenance while continuously operating in VMC conditions; unpressurized.




Synopsis: King air Captain experiences an explosive loss of cabin pressure climbing through 16;000 FT and initiates an emergency descent. ATC is notified and the flight diverts to a suitable airport.
Date: 201507
Local time of day: 1201-1800
Location: KOA.Airport, HI
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke; 10
Light: Daylight
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZHN
ATC / advisory: Center ZHN
Second aircraft: Small Transport
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; Captain
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Inbound to KOA at FL190; we were given PD to 13000 and were told [another aircraft] was westbound out of KOA. Through 14000 were given a vector of 090 and PD to 11000. [The other aircraft] then called us in sight and they were told to maintain visual with us. HCC then gave us PD to 3000. I told my co-pilot we were going to stay at 11000 until we had [the other aircraft] in sight or once they had passed.  At approximately the same time we got a TCAS (TA) telling us traffic was at one o'clock; 500 feet below us and 5 miles. We could not see the traffic because of scattered clouds. Shortly thereafter we received another TCAS (RA) 'Monitor vertrical speed' telling us not to descend; traffic was now at two miles. [The other aircraft] passed 500 feet directly beneath us. Once clear of conflict was announced we started our descent to a normal landing in KOA.Not sure why HCC vectored us toward traffic and then gave us a clearance to descend through their altitude.


Second narrative: [We] departed KOA this afternoon [and] contacted HCF center receiving a transponder code. A few minutes later we were instructed to cross the PHKO localizer and remain west of the 351-R off KOA. When we were 12 miles west of the 351-R HCF center called out [air carrier traffic] at 11 O'clock. I reported; 'traffic in sight at 11 O'clock but unable to confirm [type]'. We were instructed to maintain VFR at or below 10500; which we did. [The other flight] reported an RA to center. Center responded with; 'Roger'. We started a descent a few seconds later; they flew right over us with a separation of 500 vertically.


Synopsis: Captain of a medium transport aircraft and Captain of a small transport reported coming within 500 feet of one another in the vicinity of KOA.
Date: 202009
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
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Workload; Situational Awareness; Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate; In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Mother in row XX was extremely non complaint with her child wearing a face mask beginning during boarding. I asked her age; she told me 3 years old; so I told her the policy. She immediately became rude and said how 'every state is different' etc.; so I reiterated our mask policy and how she signed and agreed when checking in. She said she will not force her child to wear a mask and I asked that she help us as a crew to engage with her child and let her know the rules. She proceeded to argue and say she won't force her child to do anything she doesn't want to do and let her child walk all over her. FA A then tried to discuss with the mother as I stood there. We kept reiterating our policy and that we are just doing our jobs. She proceeded to raise her voice; become hostile and rude to us-- but put a face shield on her child. FA A explained the face shield rules which only upset the mother more; but we were just doing our job. FA A informed the Captain before takeoff of the situation and we asked for a Supervisor to meet the plane to explain the rules to the mother as she continued to argue with us. The mother did not enforce or comply for her child the entire time. Supervisor met the plane and took over from there.




Synopsis: Air carrier Flight Attendant reported a parent could not make a child comply with the face mask policy during boarding.
Date: 201509
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Dash 8-100
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Normal Brake System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented; Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Taxied single engine onto gate at ZZZ.  Applied normal brakes and realized no normal brakes.  Applied parking brake to stop which resulted in an abrupt stop.  I got on PA and apologized to passengers for the abrupt stop.  Passengers deplaned normally.   I also explained to marshaller why we were late in applying brakes and stopping.  I applied the parking brake which resulted in an abrupt stop.We were taxiing to gate single engine with the flaps up.  HYD standby pumps were not selected on which resulted in the number 1 HYD system not powered and therefore the normal brakes not working.  I usually double check that the standby pumps are on and functioning whenever taxiing on one engine but failed to see it this time.  I do not know why pumps were not selected on.  We should have selected them on with the final descent-approach checklist.  At any rate we missed the standby HYD pumps not selected on.I made a PA announcement to passengers apologizing for the quick stop.  Also checked with Flight Attendants (FAs) to make sure we had no injuries.  FAs stated no injuries; but that we had startled the passengers with the abrupt stop.Be extra careful when single engine taxiing with the flaps up; that the HYD standby pumps are selected on and functioning.


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


Synopsis: A DHC-8 flight crew reported they had to use the parking brake to stop the aircraft at the gate when they failed to turn the standby hydraulic pumps on; causing loss of normal brake pressure.
Date: 202002
Local time of day: 1201-1800
Location: EWR.Airport, NJ
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Ground Personnel; Person Other Person
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Spray can with Easy Off Oven cleaner removed from Crew bag.




Synopsis: Cargo Supervisor reported removing Hazmat cleaning product from crew bag during arrival inspection.