elihoole/asrs-aviation-reports huggingface dataset:
Date: 201712
Location: ZZZ.Airport, US
Light: Dawn
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Galley Furnishing
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Flight Attendants reported toxic fumes coming from coffee pot area of aft galley. They thought it was initially not that bad but when they described the smell as toxic and that all three FA's had headaches we immediately decided to divert. Initially we diverted to ZZZ but after turning north determined that ZZZ1 was closer. We informed Dispatch of divert and [advised] ATC. We ran The QRC and QRH for fumes in cockpit/cabin. One major problem was Captain's O2 mask MIC would not work making communication extremely difficult. I finally took my mask off and the FO remained on O2 until we landed. I made a PA to the Passengers informing them of the diversion due to an unusual odor being detected. After landing I called Flight Attendants and asked if we needed to egress on taxiway or if they thought we could continue to gate. They responded that the gate would be fine. After arrival at the gate I went to the aft galley to assess the situation I could not detect any abnormal odors. I made an announcement to the Passengers and we deplaned them. None of the Passengers appeared upset or showed any sign of distress.


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


Synopsis: B737 flight crew reported Flight Attendants complained of toxic smell in aft galley.
Date: 201911
Aircraft: No Aircraft
Operator: Air Carrier
Reporter organization: Air Carrier
Reporter function: Vehicle Driver
Anomaly: Ground Event / Encounter Person / Animal / Bird; Ground Event / Encounter Vehicle
Detector: Person Ground Personnel
Result: General Physical Injury / Incapacitation
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Employee was driving and a pedestrian walked into a blind spot. The employee did not see the pedestrian. Employee heard something and noticed the pedestrian had fell backwards in which she fell to the ground; got up again then stayed down on the ground in front of the tractor.




Synopsis: Vehicle Driver reported striking and injuring a pedestrian.
Date: 202001
Local time of day: 0601-1200
Location: SJC.Tower, CA
Flight conditions: VMC
Light: Night
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C SJC
ATC / advisory: Tower SJC
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Other / Unknown
Anomaly: ATC Issue All Types; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Contributing factors: Chart Or Publication; Airspace Structure
Primary problem: Airspace Structure

Narrative: Today; it was brought to my attention that an aircraft had flown within 100 feet. Of terrain at night; during a shift that I worked earlier in the week. Although I had just accepted a handoff on the subject aircraft; I was not speaking to the aircraft at the time of the event. Here are some details. At night I took the handoff from the TRACON sector for Aircraft X. Immediately after accepting the handoff; I received a low altitude alert for that aircraft. I immediately transmitted 'Aircraft X; I called the TRACON sector shout line; to verify that they were still talking to the aircraft; and they answered in the affirmative.  Approximately two minutes later; Aircraft X checked in on my frequency; and I cleared them to land. Aircraft X landed and taxied to parking without further incident.This was obviously an unsafe situation; and I am submitting this report for that reason. I did notice; after making my transmission to the aircraft in the blind; and after making the land line communication; that the aircraft was below the MVA (Minimum Vectoring Altitude) at the time of the low altitude alert. I did not expect that the aircraft would have been on my frequency; because; as I recall; I had just taken the handoff immediately prior to the low altitude alert.  Had I expected the aircraft to be on my frequency; I would have issued a low altitude alert using prescribed phraseology. In hindsight; it wouldn't have been a bad idea to just issue the low altitude alert anyway.




Synopsis: SJC Tower Controller reported they took a handoff from TRACON of an aircraft below the Minimum Vectoring Altitude and received a Low Altitude Alert.
Date: 202007
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: DC-10 30
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Distraction; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I blocked out without having signed the DG [Dangerous Goods] paperwork. During the preflight we had multiple interruptions and incongruities mostly dealing with MEL related items. The last break in the flow was a last minute discrepancy of jump seaters on the release vs. the actually number on the aircraft. The First Officer went and checked the haz-can and verified it to match the DG manifest. It was at this point in the preflight the DG paperwork needed to be signed. I was sending a message to [Operations] confirming the removal of our jump seater and just missed signing the paperwork. I later realized what had happened. We contacted the ramp and verified with them my approval of the manifest and contacted the Duty Officer who then coordinated with ZZZ to have a signed copy sent to them after landing in ZZZ1. Multiple interruptions in the preflight; not completing my final briefing/confirmation of clearance; fuel slips; and DG complete combined with inadequate signature verification. But really just set the DG manifest down without signing it. Just missed it. Take a step back and confirm all is complete before going below the line on the before start check. Another thing that would be helpful would have been getting a heads up of the js change before noticing it on the WB or a call from ramp with time and initials from [Operations] if it had already been handled.




Synopsis: MD-10 Captain reported Hazmat procedure violation of not signing DG document prior to departure.
Date: 201910
Location: UHMM.ARTCC, FO
Aircraft: B787 Dreamliner Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center UHMM
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: We requested a specific reroute due to volcanic ash. Magadan Air Traffic Controller was unable to communicate the clearance to us in English. We requested the clearance no less than 15 times; but all were incomprehensible. We requested an English speaking ATC; but the request was not understood by the Magadan ATC. This experience caused concern for all flight deck crew. We were highly uncomfortable approaching the clearance limit in Russian airspace with no further communication in English available to us. We felt that these circumstances were unsafe for the crew and passengers. Shortly before reaching our clearance limit point; we were able to log on to Magadan and receive clearance through CPDLC thereby avoiding an emergency.




Synopsis: B787 Captain reported that the flight crew was unable to communicate with ATC due to the Controller's incomprehensible readbacks.
Date: 201203
Location: ZZZ.Airport, US
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Exterior Pax/Crew Door
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was told by the caterers from the outside the 2-left outer bottom door did not close properly. The Mechanic checked the inside; never the outside. Maintenance would not dispatch the plane even though the door from the inside looked OK the outside was inoperative additionally the mechanics mentioned the mechanics at the previous station did not log the item. The plane was taken out of service.




Synopsis: A B757-200 was taken out of service when a galley service door was determined to be dysfunctional.
Date: 201602
Local time of day: 1801-2400
Location: EWR.Airport, NJ
Light: Night
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B EWR
ATC / advisory: TRACON N90
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: On approach to runway 4R; we were told to hold 170 knots to final approach fix just like the aircraft in front of us. We slowed to 170 and were approaching the FAF when we noticed we could see the aircraft in front of us and the TCAS showed them slowing down before they reached the FAF. We were very close and I was going to tell Approach we needed to slow when we were suddenly rocked hard to the right about 60 degrees. I grabbed the controls and shut off autopilot and we were rocked to the left very hard. We initiated a go around and landed 10 minutes later. We definitely were hit by wake turbulence.Suggest pilots in front wait to slow at the fix and not before.




Synopsis: CRJ-200 Captain reported encountering wake turbulence on approach to EWR.
Date: 201506
Local time of day: 0601-1200
Location: JZI.Airport, SC
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Climb
Airspace: Class E ZJX
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Distraction; Situational Awareness
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Procedure; Human Factors
Primary problem: Human Factors

Narrative: My husband and I arrived at Charleston Executive (KJZI) and saw TFR 5/2063. Later on; [we were informed] that there had been multiple changes to the NOTAM. On the day of departure; because 5/2603 went to the bottom of list of NOTAM on [software] (second to the last; and listed in the last 7 days section) and [being informed that] the TFR being effective at noon; I got confused and took the NOTAM (5/4342) as the amendment for 5/2063.  A brief was done [electronically]. An IFR plan was also filed; just in case the weather between Charleston and [the destination] deteriorated en route. I placed all my attention on getting out of Charleston Exec before XA:30 (5/4342) and avoiding ground and mid-air collisions given the busy airspace. After a normal take-off from Runway 27; I climbed to 700 feet before turning en route for a [southwest heading] for an altitude of 7;500 feet. Little did I know that I had violated 5/2063. And I was totally shocked when our airport manager told me that I should call FAA about my violation upon landing. I understand that despite the confusion; there is no excuse for me to make such a mistake as a Pilot In command (PIC). I feel extremely sorry that at such a trying time for the nation given the tragedy and large work load for the FAA; that my mistake added extra work to the good people involved. I hope that the following measures could be taken to prevent future inadvertent violations for me as well as for other pilots.  1) EducationFor pilots from states that multiple VIPs do not appear together frequently; it may be necessary to provide a VIP TFR FAASTeam course. The frequency of changes of their schedule as well as the TFRs can be really confusing. 2) TFR NotationConfusion Resulted from Multiple VIPs and multiple changes of TFR NOTAM.  If there are more than one VIP coming to the airspace; it will be very helpful if notations are put in to clarify that this NOTAM is different from the other and warn the pilots of potential confusion.




Synopsis: The pilot of a single engine aircraft became confused with the multiple revisions to the Temporary Flight Restrictions and entered a TFR.
Date: 201903
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Gate Agent / CSR; Person Dispatch
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: Approximately an hour after takeoff from ZZZ; we received an ACARs message from Dispatch indicating that our Dispatcher was called and informed that there was 437 lbs of undocumented cargo in our forward cargo compartment. We then checked the Cargo Load Report (CLR); which showed baggage information; but had no indication of any further cargo that would have been loaded onto the plane. We learned; from Dispatch; that the cargo was an electric wheelchair; and a lift. The wheelchair weighing 375 lbs; and the lift weighing 62 lbs. We requested that Dispatch recontact Operations in ZZZ and determine what type of battery was in the chair. We were then told it was a non spillable battery and was not powered on. Dispatch requested our zero fuel weight; and current fuel onboard; so that he could rerun the weight and balance numbers with the added cargo. The weight and balance was still within limits with the accurate cargo weight. During the boarding process we were not able to see a passenger being loaded onto the plane from a wheelchair. We never informed that an electric wheelchair with a battery was being loaded into the cargo compartment. It was loaded after a preflight inspection was completed on the aircraft; so it was not seen in the cargo compartment. Without being informed by the ramp crew; and the information being listed on the CLR; there was no way for the flight crew to know that the cargo was on the aircraft.




Synopsis: EMB-175 Captain reported no NOTOC of the inflight ACARs notification of undocumented Hazmat cargo [battery powered wheelchair] in cargo compartment.
Date: 201209
Local time of day: 0601-1200
Location: MEM.Airport, TN
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class B MEM
ATC / advisory: TRACON M03
Aircraft component: Autoflight System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Distraction; Situational Awareness; Human-Machine Interface
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Altitude Crossing Restriction Not Met; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Became Reoriented; Flight Crew FLC Overrode Automation
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: While descending via the LTOWN6 arrival landing north transition; the FMS was having difficulty complying with the 210 KTS at DASAC restriction. The speed had increased to 225 KTS. Distracted by the airspeed constraint; I noticed that we had descended below the 8;000 FT restriction at CLARK Intersection by 500 FT about a mile prior to CLARK. I brought this to the attention of the pilot flying and a correction was made to comply with the restriction.




Synopsis: The flight crew was forced to intervene manually when the autoflight system failed to meet the crossing restrictions at DASAC and CLARK on the LTOWN STAR to MEM.
Date: 202007
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: Champion Citabria Undifferentiated
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Flight Engineer
Human factors: Other / Unknown; Situational Awareness; Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other after mission
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I took a friend flying in the Citabria. I decided to go to ZZZ because I'd never gone to ZZZ before. After doing a full stop landing; I took off and flew back to [home airport]. In talking to a local CFI a few days later; he mentioned that ZZZ had been NOTAMED that the runway was closed without prior permission but that someone had landed there the other day. 'Oh crap' I thought. And I went back and checked NOTAMs and sure enough; you need 8 hours prior permission to land there. The NOTAM hadn't been there when I first started flying in this area late this spring. And I naively thought that an airport that small; that abandoned; and that rarely visited would have a runway closure NOTAM. It was a good lesson in complacency and I will be checking NOTAMS instead of making assumptions about every airport I go to; no matter the size; popularity; or condition.




Synopsis: Citabria pilot reported using a restricted airport without prior permission.
Date: 201810
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class G ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Sport / Recreational
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution
Contributing factors: Airport
Primary problem: Airport

Narrative: I had to land on taxiway because a plane just landed in front of me with gear up. I did not have enough fuel to go anywhere else. I had minimum fuel because this was a test flight.




Synopsis: Experimental pilot reported landing on taxiway due to low fuel state and disabled aircraft on runway.
Date: 202010
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Clear; 100
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
ATC / advisory: CTAF ZZZ
Second aircraft: Beechcraft / Beech Aircraft Corp Undifferentiated or Other Model
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Airport
Primary problem: Airport

Narrative: At approximately XA00 local time; at ZZZ at an uncontrolled field; I taxied out to the threshold of RWY XXL in biplane single place open cockpit with no Radio. Seeing [no] aircraft in the pattern or on final; I proceeded to take off. Unknown and unseen by myself; a Beech aircraft lowing four-place mono airplane was approaching to land on Rwy XXL. The Beech pilot initiated a go-around to an uneventful landing; announcing that a runway incursion had occurred. Aircraft separation was estimated as several hundred yards; and no damage was incurred by either Aircraft. Difficulty in seeing a blue and white aircraft with blue sky background; and the Aircraft was not flying the designated traffic Encourage all traffic to fly a designated flight pattern and maintain visual awareness and alert to all traffic.




Synopsis: An Experimental Biplane pilot; no radio; reported runway incursion when pilot failed to observe traffic on final; resulted in aircraft go around.