elihoole/asrs-aviation-reports huggingface dataset:
Date: 202006
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Paper CLR (Cargo Load Report) was brought to the flight deck by FA (Flight Attendant) prior to pushback.  Immediately thereafter; CARGO DOOR caution reposted.  I asked FA to verify that the CLR was accurate.  She was told (which we could overhear in the cockpit) that the count had been completed with all cargo; before they opened the door to put it in. Upon arrival in ZZZ1; the Captain noticed multiple boxes of additional company cargo; including live fish which may have been transported with dry ice.  We reviewed the CLR we had received from ZZZ ground crew.  It included no notification of additional cargo in the compartment.  Therefore; we had inaccurate numbers and thereby inaccurate takeoff and landing data.Ground crew understaffing and/or lack of communication may have contributed to the situation.  Additionally; once it was time to push; we were informed by the pushback operator; that he did not have a headset.  We were not informed prior to MCD (Main Cabin Door) closure; as would be standard.  He did not; however; engage in any signals that would've indicated a change to our cargo status.  (Of course; this would have resulted in us reopening the MCD; as CLR changes cannot be made via hand signals.)Improve the selection; training; and professionalism of [contracted] ramp staff in ZZZ.  Operational problems are a daily routine and can occasionally affect safety; as in this case.




Synopsis: CRJ-200 First Officer reported a communication breakdown between flight crew and ground personnel resulting in transporting undeclared Dangerous Goods.
Date: 201808
Local time of day: 0601-1200
Location: DFW.Airport, TX
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class B DFW
ATC / advisory: Tower DFW
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Procedure
Primary problem: Ambiguous

Narrative: On short final to RWY 18R at DFW at 200 ft AGL I saw a small white drone pass under our nose flying in the opposite direction. We took no action since it didn't pose as a threat. It was maybe 100-150 ft below us. It appeared to be flying over the construction area near the approach end of RWY 18R. I advised ATC and they had the next few aircraft land on RWY 18L.




Synopsis: Air carrier Captain reported a small white drone pass under his aircraft flying in the opposite direction.
Date: 201707
Local time of day: 0601-1200
Location: CLT.Airport, NC
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B CLT
ATC / advisory: TRACON CLT
Second aircraft: B757 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach; Flight Crew Regained Aircraft Control
Contributing factors: Procedure; Environment - Non Weather Related
Primary problem: Procedure

Narrative: On approach into Charlotte Runway 23; we were at flaps 3 and approaching the FAF LECAR which is 2;500 MSL following a B757. Very suddenly the nose of the plane dropped followed by the right wing shooting straight up. I had my hands on the controls and I disconnected the autopilot and applied the maximum amount of aileron and full power. The airplane however kept rolling. We finally exited the wake at a nose low attitude. I broke off the approach and the FO requested a heading and altitude from CLT tower/approach. We climbed to 4;000 on a 120 heading and received delay vectors until we could sort out the extensive list of EICAS messages. I tried to re-engage the automation but we lost our air data. A short time later the EICAS shortened down to AUTOTHROTTLES FAIL; WINDSHEAR FAIL; STALL PROTECTION FAIL; and ANGLE OF ATTACK LIMIT FAIL. At this point the autopilot worked again but not the auto throttles. We cleaned up the plane and accelerated to 210 KTS. I then called back to the flight attendants to check on the situation in the cabin. Everyone fortunately had their seat belts on and was fine. I made a cabin PA to the passengers; then the FO ran the associated QRH items associated with each of the EICAS messages. The FO entered the new V speeds; reloaded the approach; ran another descent checklist; then we requested vectors back to Runway 23. On the ground we received ADS 2 (Air Data System) FAIL; ADS 3 FAIL messages.




Synopsis: ERJ-175 Captain reported encountering wake turbulence on approach to CLT in trail of a B757 that resulted in an uncontrollable roll with subsequent system anomalies related to the unusual attitude.
Date: 201405
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 20
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Other / Unknown
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I called on [airport] frequency from five miles south that I was overflying ZZZ from south to north at 1;800 feet. I called again when directly over the field. At two miles north of the field an aircraft based at ZZZ overflew me at 200 feet and approximately 20 feet of horizontal separation; from my 12:00 position; each off the other's right wing. Immediately after the near miss; the [aircraft] called on the ZZZ frequency that he was two miles north at 2;000 feet and entering the pattern. I flew for another 15 minutes; [and] then returned to land.When on the ground I approached the pilot and stated I was concerned about the near miss. He stated; 'Yes; I noticed that!' It is my impression it would have been appropriate for the [aircraft] to get on the frequency and call his position and intentions from more than 2 miles out. It was very busy at ZZZ at the time--there were three aircraft on downwind when the [aircraft] entered the pattern; such that one of the aircraft felt compelled to ask where the [aircraft] was.




Synopsis: The reporter; while transiting the airspace of a busy airport; describes a near miss within 200 feet of another aircraft in the landing pattern.
Date: 201601
Local time of day: 0601-1200
Location: PHL.Airport, PA
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Aircraft component: Tablet
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While programming both the FMS and [tablet application] EFB; found that J110 appeared to be missing (it was present on the appropriate Jeppesen High chart).  Was only able to find the airway after zooming in to less than 6 mile range.  [tablet application] EFB needs to be much more complete regarding the marking of airways; both high and low enroute.  There are many examples of airway markings that do not appear until zooming in on the chart beyond a point that almost everything else becomes unviewable.  Additionally; the symbology being used; especially for VOR/VORTAC/TACAN are the same at any basic intersection.  This makes the potential for navigation error much greater.Additionally; the screen size with the iPad Mini is unacceptable; as it requires 'pinching and zooming' for just simple basic viewing of the associated approach chart/SID/STAR.  This condition is much less pronounced on the standard sized iPad screen.  I've had occurrences on every single segment flown where basic data; normally viewable on a standard navigational document; disappears from view because of the requirement to 'pinch and zoom' simply to make individual items viewable.




Synopsis: A CRJ-200 Captain reported his iPad Mini tablet Electronic Flight Bag (EFB) was difficult to use.
Date: 201202
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Aircraft: PA-32 Cherokee Six/Lance/Saratoga/6X
Flight plan: VFR
Flight phase: Cruise
Airspace: Special Use RXXXX
ATC / advisory: TRACON ZZZ
Reporter organization: Government
Reporter function: Departure; Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Other / Unknown; Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation All Types
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: My trainee allowed a PA32 to enter a restricted area. I did not notice due to my attention being focused on another problem. Recommendation: quit burning out CPCs with constant training. I have not worked a RADAR position by myself; other than on a mid shift or very early in the morning or very late at night for a very long time. Legally; I am current; but I am not proficient.




Synopsis: Controller providing OJT failed to note that the trainee has permitted an aircraft to enter a restricted area; the reporter indicating that the constant training being conducted has rendered CPC's 'non-proficient' on operational positions.
Date: 202107
Local time of day: 0601-1200
Location: ZZZZ.ARTCC, FO
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZZZZ
ATC / advisory: Center ZZZZ
Aircraft component: GPS & Other Satellite Navigation
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Ground Equipment Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: ATC Equipment / Nav Facility / Buildings; Aircraft; Environment - Non Weather Related; Human Factors; Software and Automation
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: GPS Jamming in Russian Airspace 36;000 feet from LOGMU to ROKUB.  [Cause was] Russian Jamming.




Synopsis: An Air Carrier pilot reported GPS jamming while in Russian airspace.
Date: 201909
Local time of day: 1201-1800
Location: CLT.Airport, US
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C CLT
ATC / advisory: TRACON CLT
Second aircraft: UAV - Unpiloted Aerial Vehicle
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
Anomaly: Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Human Factors; Aircraft
Primary problem: Aircraft

Narrative: On arrival into CLT from ZZZ; we were flying the FILPZ3 arrival. We were south of VALLL at 5;000 feet; talking with Charlotte Approach. We thought that we saw a small bird near our altitude. As it passes to our left; slightly above us; we noted it was not a bird. It also didn't look like a balloon. It had small contours; and we decided it could be a drone. I reported it to Approach Control.




Synopsis: Airbus Captain reported encountering a drone during descent into MCI airport.
Date: 201904
Local time of day: 1201-1800
Location: OAK.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Learjet 75
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B SFO
ATC / advisory: TRACON NCT
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Corporate
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Distraction; Situational Awareness
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Environment - Non Weather Related; Procedure; Human Factors
Primary problem: Human Factors

Narrative: Flight departed from OAK; Runway 30; OKLAND3 SID. Prior aircraft which departed ahead of us was a Boeing 737. Tower advised caution wake turbulence. After takeoff at about 1;500 feet; we experienced wake turbulence.  Both pilots were distracted by the turbulence and failed to meet the crossing restriction at D4.0 OAK. After leveling off around 2;200 feet; the Departure Controller issued new climb clearance to 5;000 feet. Contributing factor to this deviation was the fact that crew set FL190 in the altitude alerter (per the SID); instead of 2;000 feet for the crossing restriction. The crew was preoccupied with the wake turbulence and failed to level off. Flight crew notified their Safety Director and filed appropriate company safety report. The flight crew and the Safety Department will review procedures and to ensure this won't happen again on a future flight.




Synopsis: LJ75 First Officer reported overshooting a crossing restriction departing OAK when the flight crew was distracted by a wake turbulence encounter from the preceding B737.
Date: 201807
Local time of day: 1201-1800
Location: EGGX.ARTCC, FO
Flight conditions: VMC
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center EGGX
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: We were at FL340 on the track behind two other aircraft; one at the same altitude; and one at FL360. We started to pick up moderate wake; bordering on severe. I immediately offset one mile to the right; we were still experiencing the wake. I offset one more mile to the right and we started picking up the wake from the aircraft in front and above. Fearing that we would have injuries in the back; I decided to go one more mile to the right. After we offset three miles right; the wake turbulence stopped. I was going to advise ATC of our actions; but before I did that I wanted to assess the situation in the back of the airplane. While in the process of contacting the flight attendants we received a SelCal from Shanwick and they said ATC was showing us three miles to the right of course. I told them to advise ATC of our wake turbulence encounter; and to let them know that we needed to stay three miles to the right of course until 4729N; where the course changed; and the wind direction would keep us away from the wake from the aircraft in front and above. The Shanwick controller said that he was going to contact ATC; and let us know. After a few minutes; he came back and said that ATC said we only had three options; and the options were on track; one-mile right; or two. We changed our path to two miles right of course and started experiencing occasional moderate wake turbulence. We continued in the wake until 4729N. I think sometimes ATC forgets that we are not just dots on a screen; but aircraft with people inside.




Synopsis: B767 Captain reported encountering wake turbulence in cruise flight at FL340 on a trans-Atlantic route; afterwards; ATC restricted their offset to 2 miles right deviation.
Date: 201911
Local time of day: 0601-1200
Location: ORD.Airport, IL
Light: Daylight
Aircraft: Medium Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Airspace: Class B ORD
ATC / advisory: Tower ORD
Second aircraft: B777 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial; Flight Crew Multiengine
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Returned To Gate; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Weather; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: ATC cleared us to line up and wait on [Runway] 28R/N5. A B777 was cleared for takeoff prior to us taking the runway. As we moved onto the centerline of the runway; the right wing of the aircraft started to lift. The Captain had full aileron deflection to the right. We received the Mach Trim caution.  The Captain stopped the aircraft and we held until the aircraft settled. Once lined up; we decided to exit the runway and call company. As we taxied off; a pilot on an aircraft behind us stated to ATC that the wing did not make contact with the ground. I was asked by the Captain to call the FA and ask if all was ok in the cabin. She stated yes. I then asked if she felt the wing touch the ground and she stated no. We taxied back to the gate; deplaned; swapped aircraft and completed the flight. Post flight inspection showed no visible damage.




Synopsis: Air carrier aircraft First Officer reported that while taxiing into position for takeoff; their wing was lifted by jet blast from a departing B777.
Date: 201508
Local time of day: 0001-0600
Location: MMMX.Airport, FO
Flight conditions: VMC
Light: Night
Aircraft: B747 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: TRACON MMMX
Reporter organization: Air Carrier
Reporter function: Check Pilot; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness
Second reporter function: Relief Pilot; First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Approach ILS RWY 05R MEX Flight conditions night. Approaching position MAVEK aircraft was configured at flaps 20 degrees and crossing MAVEK configured gear down and flaps 25 (planning for 30 degrees) for descent from 12;000 to the next altitude of 8;800 feet for the interception of final approach to runway 05R. Upon crossing MAVEK we thought we were given a heading of 250 to fly due to closeness behind traffic ahead. I selected HDG Select and made the turn thinking this was a small widening vector for a subsequent turn to intercept final; but was concerned for terrain. Controller promptly asked what we were doing and we clarified what we thought was our assigned heading. He then gave us a right turn to 360 and a climb to 14;000 feet and then 15;000 feet. We cleaned up the aircraft to flaps 10 and re-inserted MAVEK into the FMC for a subsequent descent to 12;000 and the arrival for runway 05R. The arrival was subsequently flown with no further event.  Listen and confirm all instructions; Controller was very busy.


Second narrative: [Report narrative contained no additional information]


Synopsis: A B747 flight crew reported turning toward terrain on a night approach to MMMX when they apparently misunderstood an ATC clearance.
Date: 201911
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pressurization System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Workload
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon passing FL250 climbing to FL350 the cabin altitude began to climb between 700 feet minimum to 1;000 feet minute. Once the cabin altitude reached approximately 8;000 feet we stopped the climb and requested a descent to 10;000 feet. I used the expedited descent procedures and descended to 10;000 feet without letting the cabin altitude increase above 10;000 feet. At this point I ran fuel calculations and determined that we could make it to ZZZ at 10;000 feet; so we coordinated with Dispatch and informed them of the problem. We all decided to continue to ZZZ. The auto 1; auto 2 and manual modes of the pressurization system were working but the aircraft could not keep up with the pressurization at altitude. It appeared to be a valve stuck. However at a 10;000 feet and below there was no problem and we continued to ZZZ and landed on Runway XX uneventfully.




Synopsis: B757 Captain reported that a pressurization problem resulted in an expedited descent.