elihoole/asrs-aviation-reports huggingface dataset:
Date: 201207
Local time of day: 1801-2400
Location: HIO.Airport, OR
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
ATC / advisory: Tower HIO
Reporter organization: FBO
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Student
Human factors: Training / Qualification; Situational Awareness; Other / Unknown; Confusion; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: I came to the U.S. for flight training and today I [went] for the solo flight. The Tower called me taxi to Runway 2 via Bravo 5; and I remember last time I used Runway 2 was two months ago when I flew with my instructor; so first I taxied on B5. [Getting] closer to Runway 2; I saw the hold line; but also had a left turn taxiway in front of me and [another] hold line; so I went for the wrong direction and stopped my airplane behind the wrong hold line. When I called the Tower; the Tower gave me the right instruction; so I [went] back to the right hold line and took off. Next time I will [pay] more attention when I taxi on the ground!




Synopsis: A student pilot failed to hold at the HIO Runway 2 Taxiway B5 hold short line and was redirected by ATC to return behind the hold line before takeoff.
Date: 202001
Local time of day: 0601-1200
Location: ZHN.ARTCC, HI
Flight conditions: VMC
Light: Daylight
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
Aircraft component: Pressurization Control System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Diverted; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In level flight at 37;000 ft. we experienced a loss of cabin pressure. [ATC was advised] and we followed QRC and QRH guidance while descending to 10;000 ft. A diversion to ZZZ was accomplished next.




Synopsis: First Officer reported a loss of cabin pressure at cruise that resulted in a diversion.
Date: 202106
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: APU
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Ground Event / Encounter Other / Unknown
Detector: Person Flight Attendant
When detected: Pre-flight; Aircraft In Service At Gate
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Crew was waiting to board. On jet bridge when chemical smell very strong came upon us.  We felt like we were ingesting it.  Eyes teared throat burned. Looked at the plane and first class Galley was being boarded door was opened. That's why the smell came into the jet bridge.  I immediately got my eucalyptus spray and tried to breathe it in. I have asked for over a year for the actual ingredients and again no reply.  After being masked during boarding on the way to ZZZ. No APU. Sweltering in back of plane. Captain said was trying to get outside air. It is absolutely horrible that we have to deal with this and feel like there is a diaper on our faces. Absolutely disgusting!  Can't breathe properly; can't hear my own flying partner yesterday at all. It creates a frustration and headache asking pax and [flight attendants] to repeat themselves over and over.  This is the continuous of over a year and I wrote at that time that I do not consent to this experimental tyranny. I can't see faces; can't describe anyone and it brings on anxiety when I can't even breathe.  Being masked as a healthy person is the worst thing to do. It destroys our immune system.




Synopsis: Air Carrier Flight Attendant reported a fume event while waiting to board passengers resulting in physiological symptoms.
Date: 201605
Local time of day: 1201-1800
Location: SPG.Airport, FL
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Taxi
ATC / advisory: Ground SPG
Second aircraft: Small Aircraft
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While taxiing on Taxiway Charlie under Ground Control directives and monitoring ground frequency; a biplane was traveling the opposite direction along Taxiway Alpha. We stopped short of the intersection 'A' and 'C' by 40 yards to allow the biplane to pass by down Alpha. He was not on frequency nor did Ground Control make any call with regards to this possible yield requirements. The biplane turned right directly onto our Charlie taxiway and did not slow down. We had no option from a stopped condition to quickly move from his collision course with us. His visibility straight ahead was limited with the tail wheel configuration and he was not s-turning at all to verify taxi traffic and was not on frequency to alert him. In the last couple seconds I was preparing to shut down the engine while preparing for impact. Within 20 feet or so he turned hard right and his wing missed our prop and left wing by a few feet as he passed. [There was a] look of terror in his eyes and he waved in embarrassment as he passed by.I contacted Ground immediately and asked if they just witnessed this extremely close call. Ground response was he didn't see the biplane on the taxiway and he must have come out behind the hangars. The biplane traveled down Taxiway Alpha for at least 100+ yards prior to Taxiway Charlie in clear view of the Tower. This was a serious situation that could have easily ended in a lethal tragedy. I would appreciate talking to someone who can help me understand how all these breaches can unfold with only luck saving lives of a few people. Why wasn't the biplane speaking with ground prior to entering an active taxiway? Especially with a limited visibility aircraft. Where was the Ground Controller during the potential collision? This was an extremely serious case of broken down policy-procedure. I'm glad I'm here and able to share this with you to potentially minimize it from happening again.




Synopsis: GA pilot reported experiencing a near-collision with a biplane during taxi at SPG airport.
Date: 201706
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I departed ZZZ to do sightseeing and my passenger wanted to take photos.  [Approximately 15 minutes after departure] the engine began to run rough.  I decided to return to ZZZ where the aircraft is based.  I entered class D airspace around 2;000 feet MSL originally planning on the left base runway XY.  The tower noticed I was unusually high and they asked if I wanted [a different] runway; which I accepted and was cleared to land.  I did not declare an emergency; however the tower deemed it was an emergency; crash fire rescue was activated.  At approximately 300 feet AGL crossing the runway threshold the engine failed and the propeller came to a full stop.  After landing I attempted to restart the aircraft; which it did.  I taxied the aircraft back to the hangar without incident. No damage. The aircraft had been returned from maintenance where it underwent an annual inspection and a 5 year rubber change.  Maintenance department is still investigating.

Callback: Reporter indicated that the left fuel tank supply line and overflow line were found to have been swapped during the recent maintenance work. The aircraft had been test flown after the annual; but had only been operated from the right fuel tank. The condition was reproduced on the ground. The lines were moved to the correct positions and the system has functioned normally since.



Synopsis: Light sport aircraft pilot reported a rough running engine progressed into an engine failure. The problem was traced to fuel lines that had been incorrectly installed during recent maintenance.
Date: 201406
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skywagon 185
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Taxi
Reporter organization: Personal
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Private
Human factors: Human-Machine Interface
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: General Evacuated
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: 1974 C185 on EDO 2790 Amphib floats; 2 people on board; 70 gallons of fuel (5 knot wind to calm). After water landing; I taxied on lake for 15 minutes then went to beach to shut down; pumped the floats. I then started up; idle taxied toward center of lake; cleared area to begin a step taxi run. As soon as power was applied the prop struck water and aircraft nosed over. There was ample time to evacuate. EDO 2790 may be marginal for the C185.




Synopsis: Pilot of C185 on floats reports the aircraft nosing over when power is added to begin a step taxi. The reporter believes that the floats may be undersized for the C185.
Date: 201508
Local time of day: 1201-1800
Location: ABQ.Airport, NM
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
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)
Human factors: Communication Breakdown; Distraction; Situational Awareness; Training / Qualification; Workload
Anomaly: Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch; Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure; Company Policy
Primary problem: Procedure

Narrative: We closed out and pushed as scheduled; I failed to verify that the Passenger onboard matched the Flight Attendant count. I wrote the correct number on my yoke as 143 SOB. The loading schedule listed 110 TTL Passengers. I had already briefed a full power takeoff due to departing Runway 08 at ABQ toward the mountains. We took off as planned and while climbing to cruise altitude; we received an ACARs message from Dispatch to adjust our ZFW to 115;263. We had it as 109;463. A difference of 5;800 pounds. We adjusted our ZFW and then compared the numbers. That's where we found the difference in Passengers onboard. I should have caught the difference while doing the Before Push Checklist and verifying the weights. Our actual takeoff weight was 132;163; our actual landing weight was 124;363.




Synopsis: An air carrier Captain discovered while climbing to cruise from ABQ that the passenger manifest count was off and the aircraft weight was off by 5;800 pounds making the actual takeoff weight heavier than what was shown on the loading schedule.
Date: 201810
Location: ZZZ.Airport, US
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: We landed 22L and exited on taxiway November. There was a long 'train' of emergency vehicles driving south on taxi P as an emergency aircraft was landing behind us. Tower told us to taxi N hold short 22R emergency vehicles holding for you. They all appeared to be stopped. This exit is a 135 degree angle and from my seat I quickly lost sight of them; but as I saw them last; they all were stopped. Very shortly thereafter my First Officer told me to stop. I did without question and a large fire truck went racing past us at intersection of N and P. I never saw fire truck until he was passing in front. I have no doubt had my First Officer not been continuously looking out to the right watching the emergency vehicles a collision would have occurred. I voiced my displeasure on Tower frequency that we nearly collided. Tower gave us a number to call. After parked and checklist complete I called Tower and I explained I was not upset with them at all; but that the fire truck ignored instructions and raced past us. He said the Port Authority monitors frequencies and called due to my comments and asked if a collision would have happened if we did not stop. I replied most likely. He said they would be filing paperwork and I advised I would be filing [a safety report]. I thanked him for the great work they do.




Synopsis: Boeing 757 Captain reported an urgent stop for an emergency vehicle that had been advised by ATC to hold for the aircraft to move.
Date: 202004
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
Aircraft component: Nose Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Ground Strike - Aircraft; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Other Landing Rollout
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control; Flight Crew Returned To Gate; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: After an hour of flying from ZZZ; I was returning to land at ZZZ on Runway XX. I had received clearance to land from the Tower. I had full flaps extended and my airspeed was indicated at 75 kts. As I approached the flair; the nose dipped a slight bit. I corrected with increasing the back pressure on the yoke slightly and continued to reduce the throttle. As I bled off airspeed and the nose came down contacting the surface; it suddenly pulled to the right; causing the airplane to exit the runway into the grassy area at the intersection of Taxiway XX. I was able to get the airplane onto the taxiway and was cleared to proceed to the ramp by the Tower. As I taxied the airplane I could feel the airplane pulling to one side. Once the aircraft was shutdown; an inspection of the nose wheel indicated that it had collapsed and the fork brace that held the front wheel was bent to the right (I think).




Synopsis: PA-28A Single Pilot reported a runway excursion on landing rollout due to a nosewheel first landing.
Date: 201507
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness; Training / Qualification
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Human Factors; Manuals
Primary problem: Manuals

Narrative: The Tower Operations Manager informed me today that I did not have a certification in the tower since the end of a few months ago due to currency requirements. This was the first knowledge I had of this occurrence. A recertification was accomplished today. I have worked all positions and performed Supervisor duties [for over two months].Communicate information sooner.




Synopsis: A supervisor did not meet their Area currency requirements and did not realize it. The Operations Manager did not advise the supervisor of their currency default. The supervisor worked for several months without meeting currency requirements.
Date: 202011
Location: ZZZ.ARTCC, US
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness; Physiological - Other; Workload
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: Passenger started complaining that he was extremely hot and was grabbing at the collar of his shirt. The vents were open and the aircraft was chilly not warm. I could see that he was sweating and he asked if he could have some water.  I went to the back galley to get him water and some iced cloth folds to put on his neck.  When I turned around to head out with his items; [his condition had deteriorated].  I immediately called the pilots and we paged for medical assistance.  We had a few nurses onboard that assisted us with the passenger.  He stated he needed to get to the restroom.  I helped the nurse get the passenger to his feet and the passenger went into the lav.  He was vomiting for several minutes.I spoke with the Supervisors the next day and advised them if my concerns regarding the fact that this passenger seemed to be exhibiting COVID symptoms.  I was advised there was nothing that could be done regarding the possible exposure and that I should just self monitor while continuing to fly.  I feel that more precautions should be taken when a passenger shows symptoms of COVID mid flight.  I think we should carry a thermometer onboard and when a passenger shows COVID symptoms especially when it results in a call to medical. More precautions should be taken to protect crew members proactively instead of retroactively.




Synopsis: Flight Attendant reported possible COVID-19 exposure from an ill passenger and expressed concern the company did not have a plan for the exposed working crew.
Date: 201601
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Weather elements / visibility: Rain
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Aircraft component: Powerplant Fuel System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Second reporter function: Pilot Not Flying; First Officer
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 Flight Cancelled / Delayed
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Unable to complete Before Pushback checklist. Fuel Pumps checklist line would not close loop and show 'Green'. Right center tank boost pump pressure light remained 'on'. Attempted reset of switch including after temporarily removing all other high load electrical (fuel; hydraulic pumps). No load shed indicated on electrical synoptic. Unable get pump on. Electronic Checklist would not complete and interestingly; item and checklist override were not available. Contacted local maintenance and entered item in ACARS. Maintenance was unable to solve the problem before crew duty time expired. The next day we were told it was a 'load shed' as far as they could tell. I know that one or both center fuel pumps can shed before engine start on a single source electric (APU); any time; and the Electronic Checklist is not affected. I suspected some other problem and certainly wouldn't fly after bypassing any checklist items. Flight was cancelled.


Second narrative: During pre-pushback cockpit preparation; aircraft appeared to load shed electrically normally for fuel system center right fuel pump; but electronic before push checklist would not indicate it had. Worked with station maintenance to correct with no success. Flight eventually cancelled for malfunction. Following day; station maintenance advised that; following a maintenance turn of both engines; system load shedding of fuel pumps operated normally; including electronic checklist logic for pre-start. Suggestion was made that our crew had misinterpreted checklist on previous day. This is NOT true. Aircraft system logic had prevent us from completing the checklist; i.e.; fuel pumps line of before push checklist could not be checked Green as complete and normal.


Synopsis: B777 flight crew reported inability to complete the Before Pushback Checklist due to a persistent fuel pressure light illumination. Maintenance was unable to correct the problem by the time the crew timed-out and the flight was cancelled.