elihoole/asrs-aviation-reports huggingface dataset:
Date: 201809
Location: ZZZ.Airport, US
Weather elements / visibility: Rain
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Distraction; Situational Awareness
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object
Detector: Person Ground Personnel
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: After notifying the pilot that we were ready for pushback he acknowledged the transmission and said hold the push; because he was having problems with his on board computer. After a few minutes passed he radioed back brakes released but hold the push upon clearing of the aircraft from [the gate]. I told him that it would not impede our push but I did not move until radioed back to me that they were ready to taxi forward. I began a slow push of Aircraft X believing I had cleared the jetway; I began to turn the tail facing west to give more space between the two aircrafts. After doing so the pilot told me stop the push I immediately stopped and when I looked around that's when I was that the aircraft had made contact with the jet bridge.


Second narrative: I am extremely disappointed that this happened. The event occurred during pushback. I called for push and was instructed to hold for traffic in the alley. The captain relayed that to the push crew. Estimating 10 minutes later; we were given clearance to push. The captain told the push crew. The push commenced. Out of the corner of my left eye I caught some 'movement.' When I looked left; I saw the jet bridge. I think my words were; 'We're too close; stop;' or a very similar statement. The Captain relayed the message to the push crew. The aircraft was stopped. From the moment I saw the jet bridge until the aircraft was completely stopped was no more than 5 seconds. The brake was set. I called the Ramp Tower to inform him of the event [to] ensure that he knew that our tail may be blocking traffic. At the same time; the Captain called the flight attendants; passengers; Operations; [and] Maintenance to inform them of the unfortunate event. It was bad for everyone involved. Although we all do our very best to never damage an aircraft; sadly it happened. Thankfully no one was injured.


Synopsis: Air carrier ramp agent and flight crew reported contact was made between the aircraft and the jet bridge during pushback.
Date: 202109
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb; Takeoff / Launch
Airspace: Class B ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Workload
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [Captain reported] smoke in cockpit and cabin experienced after takeoff. Visible smoke detected in flight deck by pilots and in the cabin by [the] flight attendant. We donned oxygen masks; I assigned the flying and radios to First Officer while I ran through the QRH. Immediately returned to ZZZ and landed safely. Fire trucks inspected the aircraft once on the ground and we returned to gate under our own power.


Second narrative: Smoke in cockpit and cabin noticed around 500 feet. Smelled a burning smell then saw smoke. Flight Attendant noticed smoke coming out the cockpit door and the cabin started filling up with smoke. [First Officer] don oxygen masks and took over flying and radios. [Flight] immediately returned to the airport while the Captain ran QRH. Normal landing [followed].


Synopsis: EMB-145 flight crew reported smoke in the cockpit shortly after takeoff. Flight crew requested ATC priority handling for an immediate air return to departure airport where a safe landing was executed.
Date: 201907
Local time of day: 1801-2400
Location: SAN.Airport, CA
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground SAN
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Airport
Primary problem: Human Factors

Narrative: We were asked to expedite taxi past [taxiway] and proceed to gate. As I turned into ramp area with taxi lights on we both saw a white van approaching at a fast pace. We both watched him as I continued around the corner into the gate area. Then I realized he was not going to stop so I braked hard to avoid him. After I stopped; the white van also stopped and backed up. I do not know why he didn't see us and almost hit us.Arrest the driver. Remedial training. Distracted driving school.




Synopsis: Air carrier Captain reported braking hard to avoid a collision with a van while pulling into the ramp.
Date: 201411
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew; Person Passenger
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Took Evasive Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After takeoff the Captain (CA) and I noticed a fouled smell.  A burning smell that intensified in time.  It was my leg to fly and the CA decided to take over the control (after positive transfer of aircraft control) and decided to return the aircraft back to the airport. The CA radioed the tower and alerted them that we are declaring an emergency and to return back for immediate landing.  The tower said that we were cleared to land on runway XXR.  The flight clearance was to [fly a SID] but the tower instructed us to fly on a turn heading Northbound after takeoff.  During the turn thats when the CA and I noticed the smell.  We were on a right downwind to runways XXs when this problem occurred.  After landing successfully on XXR and cleared of the runway.  The CA and I performed the necessary checklist.  The CA then contacted the FA and she said that the smell was noticed from passengers sitting [near front of cabin].  We then proceeded to the gate with no additional problems as Emergency vehicles followed us.There were NO aircraft flying near our paths and no aircraft were told to deviate because of our path from departure; declaring the emergency; and turning towards the landing runway. Pilots and mechanics should get together and discuss the different types of odors that are associated with packs burning; electrical fires; and any other foul odor that may be encountered during all phases of flight in order identify the problem.  The CA told me once we were on the ground that [a previous] crash in the [...] started as a fouled smell in the cockpit and escalated into a tragedy.




Synopsis: The flight crew of an EMB-145 declared an emergency and returned to their departure airport after smelling a foul odor also detected in the cabin by passengers.
Date: 201410
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Aircraft: Bombardier Learjet Undifferentiated or Other Model
Operator: Corporate
Operating under: Part 135
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Descent; Initial Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Second reporter function: Pilot Flying; Captain
Anomaly: Airspace Violation All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I vectored a Lear Jet off the arrival to the ZZZZZ intersection on the RWY XX localizer at ZZZ; with a descent clearance to 3000.  The aircraft's flight path would take him over an MVA of 3000; that was the reason for the altitude assignment.  I observed the aircraft  about a mile west of the MVA between 3100-3000 and it appeared to be leveling.  The next time I noticed his altitude he was over the MVA through 2200.  I issue the low altitude alert and an immediate climb.  The aircraft climbed back to 3000 without incident.  He stated that I cleared him to descend to 2000 and read it back that way.  I thought I clearly assigned him 3000. I should have checked his altitude sooner to verify he did stop at 3000.


Second narrative: APPROACH CONTROL HAD VECTORED US OFF THE [STAR] ARRIVAL AND WERE TOLD TO EXPECT RWY XX AT ZZZ. CONDITIONS WERE VFR AND WE WERE TOLD TO PROCEED DIRECT TO ZZZZZ ON THE ILS XX APPROACH. WEST OF [THE AIRPORT] ARE SOME ANTENNAS THAT EXTEND TO A HEIGHT OVER 2000 FEET MSL.  WHILE PROCEEDING VFR TO ZZZZZ WE HEARD THE CONTROLLER SAY MAINTAIN 2000.  PART OF THE PROBLEM IN THE COCKPIT WAS THAT MYSELF; THE CAPTAIN; DID NOT HAVE MY HEADSET FOR THIS FERRY FLIGHT.  I WAS USING THE OVERHEAD SPEAKER AND WAS NOT HEARING ATC INSTRUCTIONS VERY CLEARLY BUT MY FIRST OFFICER (FO) WAS WEARING HIS HEADSET.  UPON HEARING 2000 MY FO READ IT BACK AS MAINTAIN 2000 IN A QUESTIONING TONE. THE CONTROLLER DID NOT RESPOND AND WE BEGAN TO DESCEND WITH THE TOWERS IN FULL VIEW DOWN TO 2000 FEET.UPON REACHING 2000 I ASKED MY FO; HE DID CLEAR US TO 2000?  HE SAID YES.  I STARTED TO STEER WEST OF THE TOWERS AT WHICH TIME WE GOT THE TERRAIN ALERT AND TRACON CALLED WITH A LOW ALTITUDE ALERT AND TOLD US TO CLIMB BACK TO 3000 FEET.  THE REST OF THE APPROACH WAS UNEVENTFUL.  TRACON ASKED US TO CALL THEM AND THE SUPERVISOR APOLOGIZED FOR THE POOR SERVICE THEY HAD PROVIDED. HE EXPLAINED THAT THE CONTROLLER HAD ASKED US TO MAINTAIN 250 KTS NOT 2000 FEET.  WE EXPLAINED THAT WE READ BACK MAINTAIN 2000 FEET WHICH WAS ON THE TAPE.  CLEARLY THERE WAS A BREAKDOWN IN COMMUNICATION AND THE RESULT WAS A TERRAIN ALERT IN VFR CONDITIONS.


Synopsis: TRACON Controller described a loss of separation with terrain when an incorrect read back was missed by ATC.
Date: 201205
Aircraft: B757-200
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)
Human factors: Confusion; Other / Unknown
Anomaly: Flight Deck / Cabin / Aircraft Event Other / Unknown; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Attendant
When detected: In-flight
Contributing factors: Aircraft; Human Factors; Procedure; Weather
Primary problem: Procedure

Narrative: Cockpit access and barrier; I was aft of the barrier in close proximity so that no one could tamper with the barrier during the cockpit crew's break. It got extremely bumpy. I had no jump seat to get to as there were two flight attendants already at door two working business. This is a problem. Where do I go? Should procedure be the cockpit crew always takes barrier down just in case there is this scenario? I did not feel safe not having somewhere to go. This procedure and its application continues to be problematic.




Synopsis: A Flight Attendant; monitoring the cockpit barrier during a flight crew break; was at a loss as to where to go and what to do when the ride got 'extremely bumpy.'
Date: 201908
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Turbulence; 10
Light: Daylight
Aircraft: Cessna 150
Operating under: Part 91
Flight plan: None
Mission: Other Glider Tow
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Sail Plane
Aircraft component: Cockpit Canopy Window
Component problem: Malfunctioning
Reporter organization: Contracted Service
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was the tow pilot in the tow plane. The takeoff was uneventful as well as the climb out. About 3 miles west of the field and approximately 2;400 feet AGL [the glider pilot] radioed me that the rear canopy had come loose and was open. I didn't feel anything unusual in the tow plane at this time regarding any excess drag or yaw. I looked over my shoulder through the back window of the tow plane and saw the canopy open. I asked him if he wanted me to tow him back to the airport within safe gliding range. At that time the tail of the tow plane drastically and rapidly lifted up putting me in a downward direction. Shortly thereafter the rope snapped. We both recovered from the unusual attitude and low altitude and returned back to the airport.There was no damage to the tow plane. The glider landed and some damage was recognized; mainly the rear canopy was missing and the front canopy glass had cracked; the majority of the front canopy was also missing. There was also some damage to the fiberglass on the nose section of the glider. Other light marks were noticed as well.No bodily injuries were encountered.




Synopsis: C150 glider-tow pilot reported the glider's canopy came open and the glider entered an unusual attitude; snapping the tow rope.
Date: 201310
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: Beech 1900
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
ATC / advisory: Center ZZZ
Aircraft component: Propeller Assembly
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Inflight Shutdown; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Experienced the following in flight: Number 1 Propeller would not respond properly to commanded input. After consulting Maintenance Control; we determined the need to secure the engine. We declared an emergency and landed without further event.




Synopsis: BE1900 Captain experiences a propeller malfunction requiring an in flight shutdown. An emergency is declared and flight lands safely at destination.
Date: 201710
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Distraction
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition; Flight Crew Diverted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In cruise flight en route at FL250. Smelled electrical burning followed by smoke in flight deck. Performed memory items followed by [QRH]. After performing required checklist contacted Flight Attendant (FA) and she reported to us smoke and a electrical smell in cabin. I informed ATC we need to divert. Receive radar vectors from ATC. Also informed ATC we would like to have fire rescue waiting for us once we land. During the radar vector I inform the FA to prepare cabin for landing I told we had 15 min to go before landing and that the plan was once we land we will stop on runway and have fire rescue inspect aircraft on the outside and if everything was ok we will not evacuate aircraft. Once on the ground had fire rescue inspect aircraft from outside and also they boarded the aircraft and made sure everything was ok. When inspection was done and everything was ok we taxied to the gate and had fire rescue follow us. At the gate we deplaned and informed passenger that there was another aircraft and crew coming to take them to [the destination]. All passengers and crews ok. No injuries.After talking to maintenance they believe it was pack 2. Was already flying with pack 1 on MEL and pack 2 decide to quit working.




Synopsis: ERJ145 Captain reported experiencing smoke and fumes; both in the cockpit and cabin. A successful diversion to a suitable nearby airport was accomplished.
Date: 201511
Local time of day: 0601-1200
Location: OXR.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 30
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Final Approach
Airspace: Class D OXR
ATC / advisory: Tower OXR
Second aircraft: Military
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Communication Breakdown; Situational Awareness
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: Human Factors; Airport
Primary problem: Human Factors

Narrative: I departed on an IFR flight to Oxnard (OXR). My plane is equipped with GPS (/g) and ADS-B. I was cleared by Mugu approach to fly the ILS runway 25 approach into OXR and I was told to contact the OXR tower at the marker (PARDS). At PARDS; I was established on the glideslope and localizer. Upon reaching PARDS; I switched to the OXR tower frequency. Just as I switched to the OXR tower frequency but before I had transmitted to the tower; I suddenly saw a single-engine WWII fighter plane at my 1 o'clock position about 500 feet away. The plane was in a banked left turn crossing perpendicular to my path from my right to my left. It appeared to be at or slightly above my altitude. I immediately reduced power and shoved the control wheel forward to dive below the plane. The plane passed above me; but it happened so quickly that I really am not sure how close we came to colliding. I then transmitted to the OXR tower to report that I was with them on the ILS; and I told the tower controller that I had just almost had a mid-air collision with a WWII fighter. I do not remember the OXR tower controller's exact words; but he responded with something to the effect of; 'yeah; I was just about to call you to warn you that he was turning into you.' He then cleared me to land; and I landed at OXR without incident. I had no further conversation with the controller about the near-miss. Even though my plane is equipped with ADS-B; I did not receive an aural or visual traffic alert because the [avionic] unit's 'pop-up traffic alerts' are disabled when an approach is active on the GPS. My plane has dual glideslopes and both were tuned to the OXR ILS 25; so I am certain that I was on the glideslope during the approach. My hypothesis is that the fighter was making a left overhead break over the Camarillo (CMA) airport to turn a left downwind for runway 26 at Camarillo. However; if my hypothesis is correct; the fighter was about 800 feet above the CMA pattern altitude of 877 MSL.




Synopsis: The pilot of a general aviation aircraft reported a NMAC with a warbird while on approach to OXR. The pilot received no prior warning from Approach and had not yet established contact with the Tower. The on-board collision avoidance system also did not provide advanced notice; but was likely due to the mode being disabled in approach mode.