elihoole/asrs-aviation-reports huggingface dataset:
Date: 202103
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: B777-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight; Routine Inspection
Result: General Flight Cancelled / Delayed; General Maintenance Action; General Work Refused
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was handed a [Dangerous Good Form] that included UN3077. In the ERG the narrative states under Fire or Explosion: Containers may explode when heated; and under Health: Inhalation of material may be harmful and Fire may product irritating; corrosive and/or toxic gases. I refused the items.I'm quite concerned that this type of HAZMAT was attempted to be carried on our aircraft.I tried to get further information on the goods. None were available locally at the time. I refused to carry the items.




Synopsis: B777 Captain reported refusing Illegal Hazmat cargo which was attempted to be loaded on aircraft.
Date: 202001
Local time of day: 1801-2400
Location: ZOB.ARTCC, OH
Flight conditions: VMC
Light: Night
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: AC Generator/Alternator
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While in cruise at FL370; the EICAS spontaneously displayed the 'AC ESS BUS' caution message. A few seconds later; the cockpit went completely dark. The original caution message was then accompanied by several other caution messages. The Captain (Pilot Flying) took the radios and began to call for QRH. However; the flight attendants called on the intercom before we could continue. The Captain asked me to take control of the aircraft and the radios while he spoke to the flight attendants. After a brief call; he took the aircraft and radios from me and asked for the QRH. I opened up the QRH and found the checklist for 'AC ESS BUS.' I verbalized the title and confirmed the checklist with the Captain. We then followed the procedure which directed us press the AC ESS XFER button which did not restore power. We then referenced the AC synoptic page and found that GEN 1 was magenta as mentioned in the QRH. We set GEN 1 to the OFF/RESET position and then coordinated a descent to FL 310. Upon leveling off; we started the APU. The 'AC ESS BUS' message disappeared as soon as the APU generator came online. Once the situation had calmed down; the Captain once again gave me control of the aircraft and radios so that he could brief the flight attendants in greater detail and make an announcement to the passengers. The remainder of the flight was uneventful.The cause of the incident was the sudden and unexpected failure of a major component of the electrical system.




Synopsis: CRJ-900 First Officer reported the cockpit went totally dark due to a generator failure.
Date: 201912
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While executing approach to runway in ZZZ EGPWS (Enhanced Ground Proximity Warning System) gave the terrain warning. Due to visibility being high and knowing where terrain was flight crew did not execute evasive maneuver.Due to the fact the aircraft was level doing 190 kts and was 1;400 feet AGL (Above Ground Level) I do not have a suggestion to modify EGPWS system.




Synopsis: EMB-145 flight crew reported an erroneous terrain warning during an approach in daytime VFR conditions.
Date: 201705
Local time of day: 1201-1800
Location: ZNY.ARTCC, NY
Flight conditions: IMC
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZNY
ATC / advisory: Center ZNY
Second aircraft: B777-300
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Regained Aircraft Control; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: ATC instructed us to climb from FL320 [to] FL340; we were IMC. Upon reaching close to FL340 aircraft suddenly encountered wake turbulence and rolled sharply to the left; autopilot disconnected and we received aural 'bank angle' warning. I believe the aircraft was around 45-50 degrees bank. I rolled wings level; we notified ATC; offset to the left and began a descent back to FL320. The seatbelt sign was on at the time. We called back to Flight Attendants who reported no injuries; but said one passenger was standing in the aft of aircraft and fell over. ATC informed us the traffic ahead of us was a 777-300 at FL340. I believe we were around 8-10 miles in trail. ATC offered us a climb or descent and offset up to 4 miles. We experienced no further wake after the initial event.




Synopsis: B737 Captain reported encountering wake turbulence at FL340 8-10 miles in trail of a B777 that resulted in a 'sharp' 45-50 degree roll to the left.
Date: 202010
Local time of day: 0001-0600
Flight conditions: VMC
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Flight phase: Takeoff / Launch
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Communication Breakdown
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure
Primary problem: Procedure

Narrative: Following a weather brief ( winds 130/03) and unicom radio check (in which we were confirmed to be 'loud and clear' by the FBO dispatcher); my student and I declared on the CTAF frequency that we were taxiing from the FBO tie downs to the run-up area for runway 5. Prior to entering the taxiway from the tiedowns; both my student and I cleared left and right for traffic on the taxiway. After our engine run-up; we announced that we were taxiing from the run-up area to runway 5. Prior to takeoff; we heard another pilot announce that he was landing on runway 5. While holding short of 5; we cleared the approach end for 5 and 24 and announced that we were departing runway 5. There were no additional radio calls from time of  taxi to takeoff; other than 1 inaudible transmission. Shortly after departure (I assume around a couple hundred feet); an airplane approached head-on from the opposite runway then quickly veered off to the right (left of our course). After review of the time stamp (ADSB out); it is to my knowledge that both aircrafts had departed from opposite runways.




Synopsis: Flight Instructor reported at take off seeing opposite direction traffic resulted in evasive action.
Date: 201409
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Private
Human factors: Other / Unknown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I inadvertently landed on a closed runway.  I was unaware of the runway closure; which I subsequently discovered had just gone into effect that morning.  I did not see the runway closed markings and after landing saw cones blocking the entrance to the ramp from the taxiways; so I took off and after circling; saw the yellow x markings which were placed off the ends of the runway in grass; not on or near the runway numbers which were clearly visible.  In addition to less than optimal runway closure markings; I had not noticed any posted notice of the planned closure despite flying into the airport and walking through the terminal building multiple times in the last few weeks.




Synopsis: C210 pilot reports landing at a closed airport which was not detected until after landing. The reporter elects to depart and while circling after takeoff; yellow X's are noted off the end of each runway on the grass.
Date: 201204
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B747-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Workload; Distraction
Anomaly: Inflight Event / Encounter Bird / Animal
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: After a normal taxi out and takeoff; a loud deep rumbling noise began as the gear was retracted.  No yaw; vibration or abnormal engine indications were noted except for #1 engine N1 vibration indicator at 5.0.  I reduced Engine 1 to idle and the noise stopped.  When the 'Engine Limit/Surge/Stall' QRC was accomplished and thrust for Engine 1 was advanced and the rumbling noise did not return but 3 compressor stalls were experienced as power approached the climb thrust value.  Engine 1 EGT never moved from the normal range and was operated at idle power for the remainder of the flight.  After consultation with Dispatch and Maintenance; fuel was dumped to achieve max landing gross weight and we returned to the departure airport.  At no time during this sequence did I declare an emergency or ask for emergency equipment to be standing by.  We did receive priority handling by ATC and emergency vehicles were in position as we landed.  The Lead Flight Attendant was advised that no Prep for evacuation was required and that they should follow normal approach and landing procedures.  After parking at the gate; Maintenance observed Engine 1 compressor blade damage and a blood trail in the aft engine area.  No birds were observed during or after takeoff by any of the cockpit crew.




Synopsis: A B747-400 developed a 5.0 engine vibration after takeoff; and after the thrust was reduced then advanced compressor stalls resulted so as a precaution the flight returned to the departure airport. Apparently a bird was ingested during takeoff.
Date: 201906
Local time of day: 1201-1800
Location: LGA.Airport, NY
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B LGA
ATC / advisory: TRACON N90
Second aircraft: UAV - Unpiloted Aerial Vehicle
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: Situational Awareness; Distraction
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Procedure; Aircraft
Primary problem: Aircraft

Narrative: We were descending from 7;000 feet to 4;000 feet proceeding direct to the DIALS intersection. I was the pilot flying the airplane. At approximately 4;500 ft.; the First Officer; pointed out an object at approximately 10 o'clock to our position. It took me about a half second to process what the object was. At first; I thought that it was a mylar balloon but then it looked more like two spheres connected together vertically. The object was dark in color and I would approximate the spheres to each be 2 feet in diameter. As the object was at about our 9 o'clock position; we determined that the object was a UAV. By that time; we were already passing the object and there was no time to react. From the moment of detection; until the object was safely past our wing was approximately 3 seconds. I would estimate that our left wing came within 200-500 feet of the object; however; I cannot be sure how close (or far) we came from it due to the short time that we saw it. Immediately after passing the object; we notified approach control of the encounter.




Synopsis: Captain reported encountering a UAV while in descent for landing to LGA.
Date: 201308
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
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: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Elevator
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Maintenance Action; General Declared Emergency
Contributing factors: Procedure; Aircraft
Primary problem: Aircraft

Narrative: During the climb after passing through FL310 the control column started to vibrate similar to the vibration of the stick shaker.  The vibration could also be felt by the Flight Attendant through the floor of the aircraft.  The vibration was very low in frequency when it first occurred then during the descent it changed to a very high frequency to the point where my hands felt very numb after landing.  We declared an emergency; applied the structural damage QRH procedure; did a phone patch with the company and air-returned.  The threat was that the control column was shaking and it was due to the elevator control surface failure.    The other threat was that the company lied to me and told me over the phone patch that they did not have any information or knowledge of this issue with this aircraft.  On the ground I found out from the Maintenance; and Engineering folks that met the aircraft that they have had this issue before with this aircraft.  Other than the structural damage QRH procedure there really is no procedure for what happened.  The Maintenance and Engineering folks that met us upon arrival; informed us that this issue has happened previously with this aircraft.  During flight when I had the phone patch to Dispatch I very specifically asked if Maintenance Control had any knowledge of this issue and at that time they lied to me and said no.  Then on the ground I find out that they did know about it.  They could have at least passed that information and that the plane didn't crash when it happened before; which would have at least lowered my stress level.




Synopsis: EMB145 Captain experiences control column vibration climbing through FL310.  After discussions with Maintenance an emergency is declared and the flight returns to the departure airport.  The aircraft had  a history of elevator vibrations but this information was not relayed to the crew while airborne.
Date: 201910
Local time of day: 0001-0600
Location: ZZZ.Tower, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Training / Qualification; Communication Breakdown; Time Pressure
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: I was with an instrument student practicing landings; we did a touch and go on Runway 9 at ZZZ and were going to make a full stop landing. We were instructed to make a right traffic pattern and once on the right cross wind I asked Tower if I could land on Runway 5 and hold short of Runway 9 being that I knew there was another airplane in the pattern. Tower then cleared me to land Runway 5 and hold short of Runway 9. My student then made an approach to Runway 5 and ended up bouncing the landing and began to porpoise. As I went to take control the aircraft the student went full throttle to go around. We then climbed to about 80-100 ft. and I looked to our left and the other aircraft was on the departure leg for Runway 9 and we were on a collision course when I kept the airplane in ground affect causing us to pass slightly in front of the other aircraft and below it.




Synopsis: PA28 Instructor reported student go around resulting in a NMAC with crossing traffic.
Date: 202010
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: First Officer; Pilot Flying
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure; Aircraft
Primary problem: Environment - Non Weather Related

Narrative: Climbing to 7;000 feet with Aircraft Y traffic at 8;000 feet MSL.  Turning from departure heading of 035 to assigned heading of 320.  Received a TCAS TA and a TCAS RA at about 6;700 feet MSL to 'Level Off.'  Complied with the RA and notified ATC.  Traffic passed above and behind us.Climbing turn near traffic with light aircraft climbing faster than normal (235;800 lbs).Shallow climb rate near traffic.  We were very light with a takeoff gross weight of 235;800 lbs.


Second narrative: We were climbing to our initial level off altitude of 7;000 feet on a 035 heading. Departure alerted us to traffic at our 12:00 O'clock at 8;000 feet and had us turn to 320. At approximately 6;700 feet; the TCAS alerted us to traffic and then in the turn leveling at 7;000 feet the TCAS alerted us with an RA to level off. We complied and traffic passed behind us. We alerted ATC of the RA and are filing this report.Light aircraft (235.8 lbs) out of ZZZ maybe confused departure and we climbed to altitude faster than other airline aircraft usually do. Also busy terminal area with lots of GA traffic all could be potential causes. No one felt threatened likely in either aircraft but RA did go off.Earlier vector from departure away from oncoming traffic despite altitude separation.


Synopsis: Air Carrier flight crew reported over shooting an assigned altitude with a light aircraft; resulting in an airborne conflict.