elihoole/asrs-aviation-reports huggingface dataset:
Date: 201807
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: APU Pneumatic System & Ducting
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Time Pressure; Workload
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution
Contributing factors: Aircraft; Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: Just after rotation an acrid smell was detected followed shortly by unusual colored smoke/fumes mostly on the FO's side of the airplane. The FO immediately put on O2 mask because he didn't feel normal. On downwind; I called the FA's and number 1 reported that she didn't smell anything. We performed the QRC Smoke/Avionics smoke/fumes soon after detecting the acrid smell and this lessened the impact. After gate arrival; I was informed by flight attendants they were experiencing nausea and headaches plus the FO wasn't feeling well either. Oddly enough; I'm not aware of any passengers requesting medical assistance. After deplaning; FA's and FO's condition got worse so we requested medical assistance from airport EMT's. I know the EMT's administered meds to FO as well a IV bag plus the EMT's evaluated all crew then they released us to go to hospital. Since event occurred on the weekend; there seemed to be some confusion on what local facility could see and treat the crew for their medical condition. Also; local operations couldn't provide transportation for entire crew to the hospital. This caused some delay in getting the crew to a local hospital for treatment. The flight [crew] was taken by ambulance to hospital and I'm not sure who took FA's to a different hospital. For some reason the FA's were taken to a different hospital than the flight [crew] even though I requested we all go to same facility. Thanks to local chief pilot for making things happen in regards to getting us to local hospital for immediate care because I eventually started experiencing a headache and facial flushing. I don't believe I was functioning at a high level and this point. I was informed a day later that there was a leak in the APU system allowing fluid to get into aircraft air conditioning system. ZZZ needs to have a protocol in place for medical events that occur when their normal medical facility is closed. It shouldn't be up to the crew to determine what is a appropriate medical facility to go to for treatment.




Synopsis: A320 Captain reported acrid smell and smoke after rotation resulted in a return to the departure airport and the crew being transported to hospitals.
Date: 201911
Local time of day: 1201-1800
Location: ZOA.ARTCC, CA
Light: Dusk
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZOA
ATC / advisory: Center ZOA
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Commercial
Human factors: Confusion; Communication Breakdown
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Human Factors; Chart Or Publication; Procedure
Primary problem: Chart Or Publication

Narrative: While in cruise flight on the SERFR 3 Arrival; Oakland Center cleared us direct to the NRRLI way point.  We mistakenly selected the NARWL way point and began navigating to that fix. After a minute; ATC queried our track and asked if we were going to NRRLI. Recognizing our error; we reprogrammed the FMC to change our course for NRRLI. ATC indicated that this was a common error and that they were in the process of making a change to the arrival.  In the future; I will be more aware of this deviation while on the SERFR Arrival and be careful before making any changes to fixes in the FMC.




Synopsis: B737 First Officer reported navigating to wrong; similar sounding; waypoint on STAR.
Date: 202007
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: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown; Distraction
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors
Primary problem: Company Policy

Narrative: During boarding; FA B did not feel safe having a guest seated close to them in XXD. FA B asked guest to move across to XXC or B. Guest refused. FA informed the rest of the crew to the situation; and we called a CSA down to re-seat the guest. Guest refused to change seats; even for a free upgrade to premium; and started acting harshly toward FA B; and CSA. He sprawled out in his seat; and would not listen to any explanation given by the crew or CSA. At that point; his cooperation with the exit row duties came into question; and with guests behind him growing restless and more aware; the CSA made the decision to remove him from the flight. Unless the flight is full; please block seats XXDEF on the aircraft. It is not safe for either guest or crew member to sit directly across from each other; less than 6 feet apart.




Synopsis: Flight attendant reported they asked a passenger to move to an upgraded seat for social distancing purposes; but the passenger refused.
Date: 201507
Local time of day: 1801-2400
Location: RIC.Airport, VA
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: Ramp RIC
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other push back
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Ground personnel completely unfamiliar with push and tug procedures. Push crew disconnected from aircraft without calling for parking brakes. Would not connect after flashing landing lights. Attempted to tug aircraft without communication and parking brakes set. Non-SOP terminology and attention to safety.




Synopsis: A319 First Officer reported the push back ground crew seemed to be completely unfamiliar with push back and tug procedures.
Date: 202010
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: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion; Distraction; Situational Awareness; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed
Contributing factors: Company Policy; Environment - Non Weather Related; Procedure; Human Factors
Primary problem: Human Factors

Narrative: Yet again we are having problems with passengers not wearing their masks when told to; multiple times. In this case a passenger was told repeatedly by the purser to wear his mask. He was irritated and would not comply. I made a PA announcement to reinforce the purser's statements to him. He reluctantly complied; but then continued to be disruptive so the purser and I decided he should be removed from the aircraft. We called for a Supervisor to assist. The passenger was removed to the jetway where a heated discussion took place. I made it very clear that I wanted the passenger removed from the flight. Several supervisors showed up and again my decision to remove this passenger was second guessed. This went on for 30 minutes. In hindsight I guess I should have called Operations to end this never-ending discussion going on between the passenger and supervisors; but I shouldn't have to resort to that. I wanted the passenger removed and it wasn't happening. To not delay all our other passengers further the purser and I agreed to take him back on the aircraft. Later in the flight the passenger was intimidating the purser by staring at her and lowering his mask below his nose.




Synopsis: Air carrier Captain reported wanting to remove a passenger for not complying with face mask policy; but was over ruled by supervisors. The passenger intimidated the Purser during flight and was still non-compliant with face mask policy.
Date: 201908
Local time of day: 0601-1200
Location: N90.TRACON, NY
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B EWR
ATC / advisory: TRACON N90
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Human-Machine Interface; Other / Unknown
Anomaly: Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was First Officer/Pilot Monitoring; Captain was Pilot Flying.  We were cleared to 'Descend via the PHLBO3RNAV Arrival.'  Properly briefed by Captain; reviewed by First Officer/Pilot Monitoring.  During descent First Officer/Pilot Monitoring turned off screen of EFB to preserve battery life; on assumption that briefing was done properly; this was a 'Routine operation conducted numerous times in recent past;' info was duplicated in FMS; and Captain was also a more experienced pilot who had a decade more experience than First Officer and 'had the procedure memorized.'  Altitude set to 11;000 [feet] for SOMTO; no issues.  Passing SOMTO; Captain/Pilot Flying set altitude to 7;000 [feet] (as opposed to correct 8;000 [feet]) for DYLIN; and announced '7;000 set.'  I; as First Officer/Pilot Monitoring; responded'7000 SET' and confirmed setting; without noticing error and thus taking corrective action.  We descended to 7000.  No comment from ATC; who handed us off to next Controller.  It was THAT Controller who questioned us about the 7;000 feet altitude; advised that it was 'no big deal' while pointing out we were supposed to be at 8;000 [feet]; and then had us continue descending to 5;000 feet to continue approach to Newark 4R.  Captain and  First Officer debriefed that neither one of us caught the obvious error; and agreed we had been 'conditioned' to expect 7;000 feet from the much more frequently used (by us at least) CRANK at 7;000 feet of the FLOSI3RNAV Arrival from the north. 1;000 feet lower than expected at that portion of the arrival procedure and during ATC hand-off. Do NOT try to stretch battery life of EFB at the expense of being able to properly monitor the situation.  Read the procedure EVERY TIME IN DETAIL; even if it is one which you THINK you are familiar with.




Synopsis: Air carrier flight crew using EFB charts turned off EFB to conserve battery life. During STAR arrival; an altitude was missed and ATC notified the crew of the deviation.
Date: 202103
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Avionics; Maintenance Powerplant
Human factors: Distraction; Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Other Post departure
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X in ZZZ reported possible low pressure of crew Oxygen. I have prepared a crew oxygen cylinder as a Fly Away Kit to load on rescue aircraft without following the Dangerous Goods shipping procedure. I have totally forgot that oxygen cylinder was a Dangerous Good. Aircraft departed [date/time] for ZZZ.




Synopsis: Air carrier Avionics Lead Technician reported he neglected to list Oxygen Cylinders as Hazmat shipment.
Date: 201409
Location: HOU.Airport, TX
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZHU
ATC / advisory: Center ZHU
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Human-Machine Interface; Situational Awareness
Anomaly: ATC Issue All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Chart Or Publication; Human Factors; Procedure
Primary problem: Chart Or Publication

Narrative: Routine flight to Houston. Cruising at FL 340; we were initially cleared to descend a few thousand feet by Houston Center and then subsequently cleared to 'descend via' the KIDDZ 1 Arrival into Houston Hobby. I brought up to my First Officer that the controller neglected to issue a runway transition with the clearance and asked him to clarify. When asked what runway; the controller responded that he had no idea what runway they were using at Hobby. Another aircraft on the frequency piped in and told the controller that we need that information in order to comply correctly with the 'descend via' clearance. The controller responded and basically said they were trying to make it work but were short of having it all together. We elected to set the lowest altitude on the main portion of the arrival; not associated with a runway; which was 9000 feet at GLUVR; and feel that was correct in light of the situation. This Center Controller handed us off to Houston Approach who subsequently cleared us for the Runway 4 transition; after which we reset the MCP to 6000 feet. This was the first time that I can remember receiving a 'descend [via]' clearance without a runway. Flight continued uneventfully and landed at Hobby without any further ATC issues.Coordination between Center and TRACON would be helpful. I find it hard to believe that Center had no way of knowing what the landing runway was at Hobby. My understanding is that we need this information to fully comply with the arrival.

Callback: The reporter stressed that no attempt was made by Center to obtain the runway information. Reporter added that the flight crew unilaterally elected to utilize the altitude crossing at GLUVR as their required 'bottom' altitude; notwithstanding the bottom altitudes on all of the subsequent routings to the runways.



Synopsis: When the B737 flight crew was cleared to 'descend via' the KIDDZ1 RNAV STAR to HOU; the crew was unable to complete programming the STAR until ATC provided the expected landing runway. STAR tracks and altitude restrictions beyond GLUVR are dependent on programming the associated runway. When asked; the Center Controller advised they had no idea which runway was in use.
Date: 201310
Local time of day: 1201-1800
Location: N90.TRACON, NY
Flight conditions: VMC
Weather elements / visibility: Thunderstorm
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
ATC / advisory: TRACON N90
Aircraft component: Altimeter
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: We were out of 9;000 FT for 8;000 FT when I noticed amber dashes on altitude alerter. We had gone into pitch mode; and we noticed that the First Officer (Pilot Flying) had a red 'X' that appeared on his altimeter. He selected ADC1; and I ran the QRH. The aircraft had gone into heading mode inadvertently as well; and we momentarily headed left of course on our way from MERSR to METRO. We immediately began proceeding to the right to join our course; and as we did; ATC asked if we had navigational issues. I advised them that we had a minor maintenance issue and were once again joining back on course. They accepted; and we joined our proper course to METRO without incident. We had already had Pack 1 MEL'ed on the aircraft; and during flight; we kept getting an RA1 flashing; indicating RA2 had quit.  This was sporadic and would disappear. During our descent on the PHLBO arrival; we got the failure on the First Officer altimeter tape.  Additionally; the weather was marginal; with low ceilings around 500 FT; and visibility 4 miles. Regardless of what mechanical issues present themselves; I must remain constantly aware of the aircraft position. Broken clouds and rain.  We were in and out of clouds.


Second narrative: In flight altimeter 2 failed on descent from 8;000 FT to 6;000 FT. this kicked off the Nav guidance along with the vertical guidance. We put the airplane into heading mode in order to run the QRH and forgot to re engage Nav mode after QRH was complete. I noticed that we were off course and noticed that we were still in heading mode. Started a turn to intercept course to MARRT and ATC queried about what we were doing. We notified them that we had a mechanical issue which caused the deviation and they recleared us direct MARRT to rejoin the arrival. Navigation kicked off was the threat. Not sure why it was kicked off for an issue that was with the altimeter. Just remember what mode the autopilot is set in.


Synopsis: EMB145 flight crew experiences an altimeter failure during descent causing the autopilot to disengage. Heading mode is selected while the QRH is consulted and NAV is not selected until after a track deviation occurs.
Date: 202201
Local time of day: 0001-0600
Location: ZZZZ.ARTCC, FO
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On the descent into ZZZZ passing approx 7-10k ft. and passing through a moisture layer; a very strong chemical odor similar to paint entered the cockpit. I immediately had several physiological responses to include dizziness; brain fog; muscle fatigue; and a tingling sensation throughout my body. The event lasted approx 30-45 seconds. I contacted Med on the ground and they directed me to get a medical evaluation at a local clinic. I returned from the clinic and tried to get some rest for the night but a general feeling of unwellness and anxiety kept me up half the night. I decided the safest course of action would be to call out mid pairing sick for my return leg.




Synopsis: A320 Pilot reported a fume event during descent characterized as a 'very strong chemical odor'. Reporter experienced multiple physiological symptoms.