elihoole/asrs-aviation-reports huggingface dataset:
Date: 201404
Local time of day: 0601-1200
Location: ORD.Airport, IL
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke
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 ORD
ATC / advisory: Tower ORD
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Fatigue
Anomaly: Deviation / Discrepancy - Procedural Landing Without Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was hand flying a visual approach to 28C; I was staying about a dot high to avoid the wake of the B747 we were following. We were cleared for the visual and to contact Tower at the marker. It was not until after landing that I realized the freq was not switched over. The First Officer and I were discussing how Chicago Approach will leave you on Approach's frequency to adjust your speed until the final fix; as he was unfamiliar with Chicago. I may have landed without a landing clearance. We contacted Tower ASAP and made corrections.  I was feeling very tired during the flight to ORD; and I think I was experiencing micro sleep during the flight. I knew that I was not fit for duty so I called off fatigued. My concern is that when I called Scheduling to call off fatigued; the person on the phone started asking me all sorts of questions about why I was fatigued. I felt like I was being bullied about calling off fatigued; she also stated; 'are you just trying to get released from work'. I said no I don't know what you are talking about I am fatigued and not safe to fly. I had to ask for a hotel and what was planned for me after that. This company needs to stop retaliating against people when they aren't able to do exactly what the company wants or thinks we should do. Its causing huge safety issues and they don't care what the results are they just pressure you or try to make you do things for fear that your job is at stake. The company pressure's pilots to work in unsafe situations; because they do retaliate against us and they create an unsafe work environment by making pilots feel that there job is at risk for making judgment calls that we need to make.




Synopsis: EMB175 Captain reports landing without clearance which he attribute to fatigue. A fatigue call is made to scheduling and is met with some resistance.
Date: 202009
Local time of day: 1801-2400
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Workload; Communication Breakdown; Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: Family flying together not complying after being asked many times to wear their mask when not eating or drinking beverage.  Traveling with group of 9 passengers.Passengers not complying with wearing their masks after being asked to many times.




Synopsis: Flight Attendant reported a family; part of a traveling group; were not compliant with face mask policy.
Date: 201505
Local time of day: 1801-2400
Location: PVD.Airport, RI
Light: Dusk
Aircraft: Small Aircraft
Flight phase: Landing
Airspace: Class C PVD
ATC / advisory: Tower PVD
Reporter organization: Government
Reporter function: Flight Data / Clearance Delivery
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Situational Awareness; Confusion; Communication Breakdown
Anomaly: Airspace Violation All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Landing Without Clearance; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During a TFR event at the OQU airport with a few restrictions in place. Aircraft X; not talking to PVD approach control or PVD tower landed at PVD on Runway 5. The aircraft was not in communication with any personnel at the PVD facility. I was working Tower Clearance and another controller was on Local/Ground/CIC combined. He had an air carrier aircraft from the arrival controller; cleared him to land.  After he was cleared to land the Local Controller (LC)/Ground Controller (GC) scanned the runway and noticed Aircraft X was nearly touched down. He immediately asked who is that guy? I immediately picked up the phone to call downstairs and reported that we had an aircraft land opposite direction Runway 5. The LC/GC then canceled the air carriers landing clearance and I told him to put him on a 140 heading maintain 2;000 feet.  We tried to contact Aircraft X several times on the tower; ground and guard frequencies numerous times. The aircraft taxied to the ramp and was met by airport operations. The ASDE-X did not go off and no loss of separation occurred. No recommendations. Keep scanning.




Synopsis: PVD Controller reports of an aircraft not talking to approach or Tower lands opposite direction with a carrier on final to the landing runway. Carrier was sent around and controllers attempted to talk to landing aircraft but there was no answer. Aircraft taxied to parking and was met by airport operations. ASDE-X did not alarm.
Date: 201510
Local time of day: 1201-1800
Location: EWR.Airport, NJ
Flight conditions: VMC
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B NYC
ATC / advisory: TRACON N90
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Workload; Distraction
Anomaly: Airspace Violation All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: Near miss with Drone; while on final approach to 04R we saw a drone about 1-200 feet below us barely off centerline of 4R. We were at 2000 feet and cleared for ILS 4R had we been 200 feet lower we would have hit the drone. It was reported by several other aircraft prior to our sighting. I made phone call to TRACON as requested and subsequently got a few more calls throughout the day from Dept of Homeland security.




Synopsis: A heavy jet Captain on final to EWR 4R reported an Unmanned Aircraft System near miss at 2;000 feet when the craft passed beneath their aircraft.
Date: 201906
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew; Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During our takeoff roll both the Captain and I noticed an unusual smell. Shortly after we rotated the smell intensified quickly. At roughly 800 feet AGL the FAs called the cockpit to report the same smell in the back of the aircraft. They stated it was intensifying quickly. Both the Captain and I agreed the smell was of burning engine oil and we quickly donned the O2 masks. We stopped the climb and [requested priority handling] with ATC. The Captain began running the Smoke/Fumes Checklist; but we both agreed it was not proper for the event we were experiencing and we didn't have the time to complete the necessary steps and prepare for landing.We focused our attention on safely and quickly returning to the ground as we were concerned for the safety of our cabin crew and passengers. The Captain quickly briefed our passengers that we were aware of the smell and were returning to the field. We ran our necessary checklists; retrieved our landing data and landed. We stopped on the runway and allowed CFR (Crash Fire Rescue) to inspect the aircraft for any noticeable issues outside the aircraft. They cleared us of any obvious external issues and we returned to the gate.We were informed that the aircraft had an engine wash the night before. Maybe doing a high power run prior to returning the aircraft to service; while operating the packs to verify the system is clear of any contaminates that may have been dislodged or blown into the bleed valves/system.




Synopsis: B737-700 First Officer reported unusual odor during takeoff roll which intensified during initial climb. Flight executed a return to departure airport.
Date: 202004
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: UAV - Unpiloted Aerial Vehicle
Operating under: Other 107
Flight plan: None
Mission: Utility / Infrastructure
Flight phase: Cruise
Airspace: Class C ZZZ
Reporter organization: Corporate
Reporter function: Other / Unknown
Reporter qualification: Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Other Person
When detected: Other post flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Arrived at location for a roof inspection. I checked airspace with the Airmap application on my phone. Airmap listed the location was just outside of the Class C airspace of ZZZ. No flight plan was filed and the UAV roof inspection was performed. It was not until later when our drone coordinator was performing airspace reviews that he found the violation had occurred. I am unclear that the initial search in Airmap showed the location was in uncontrolled airspace. Going forward; I will cross reference airspace with other applications when searching airspace requirements to ensure that I am looking at the right location.




Synopsis: UAV operator reported becoming aware of an airspace violation after flight had terminated.
Date: 202007
Local time of day: 1201-1800
Location: BDR.Airport, CT
Weather elements / visibility: 10
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
Airspace: Class D BDR
ATC / advisory: Tower BDR
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport
Primary problem: Airport

Narrative: Multiple pilots are reporting that the trees on the final approach course to Runway 24 are very close to aircraft and may need trimming.These trees are on Airport property on the approach to Runway 24 and seem to be close when making the RNAV Runway 24 approach and reaching minimums. Tree trimming would be an easy fix.




Synopsis: Instructor pilot reported trees need trimming near final approach for safety at BDR airport.
Date: 202010
Local time of day: 0601-1200
Location: MMFR.ARTCC, FO
Flight conditions: VMC
Light: Daylight
Aircraft: B737-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center MMFR
Aircraft component: MCP
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Diverted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Just after entering Mexico airspace flying level at FL 350. The autopilot kicked off and the flight director disappeared. We lost all functionality of the MCP panel. I decided to return. We requested radar vectors back to US airspace. When in US airspace we advised ATC and got radar vectors. I contacted the company via AIRINC and informed them of our situation; and requested latest weather. Cause unknown. Performed air return.




Synopsis: B737 Captain reported loss of MCP; autopilot and flight director; which resulted in diversion.
Date: 201905
Aircraft: B747-400
Operator: Air Carrier
Operating under: Part 121
Flight phase: Other Non-Flight
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Other Person
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors
Primary problem: Company Policy

Narrative: I have just been informed by [Company] that during an internal AIMS audit; the company discovered that the crew scheduling rule in the AIMS system which impacts three FAA regulations was inadvertently turned off. As a result; I may have exceeded: 14 CFR 121.471(a) resulting in flying in excess of 30 hours in a 7 day period. Due to the complexity of our operations throughout the world; I suggest keeping all FAR 121; 117; domestic and international operations separate from each other and flown by a set of dedicated crew members. This allows us to better monitor our own schedules and help prevent this kind of error in the future.




Synopsis: B747 Captain reported notification by company audit department of FAR Flight Time Limitation violation due to company monitoring system error.
Date: 201906
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Environment - Non Weather Related; Human Factors
Primary problem: Aircraft

Narrative: Delays were taken to assess and troubleshoot ongoing navigation issues specific to CRJ aircraft. Flight departed to ZZZ. On takeoff; it became evident a discrepancy between MFD Map and VOR green needles was occurring although corrective action to prevent this issue was taken while on the ground during delay. MFD Map placed aircraft very far from actual location. Pilot Flying was operating in white needles with auto tune on. Pilot Monitoring switched from whites needles to green needles to verify VOR signal. Upon recognition of navigational discrepancy; ATC queried our heading then assigned vectors. Radar vectors requested the rest of flight. Issues with navigation satellites specific to CRJ aircraft. Aircraft had difficulty establishing its location in auto tune mode.  Instruction on the use of auto tune and verification of accuracy on ground prior to departure.




Synopsis: CRJ-700 First Officer reported problems associated with GPS navigation.
Date: 201908
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Second aircraft: Airbus Industrie Undifferentiated or Other Model
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; Time Pressure; Confusion; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were taxiing out of the north ramp area from Gate XX. We were cleared by ZZZ Ramp Control to taxi out. We contacted ZZZ Ground Control and the Controller gave us a taxi clearance to taxi to Runway XXL and to follow an [Aircraft Y] coming from our left on the taxiway. Both my FO (First Officer) and I understood this clearance and my FO read back the clearance correctly to the Ground Controller. Then a short time after that; the Ground Controller told an aircraft (that was taxiing behind the above mentioned Airbus) to give way to the [Aircraft X] (us). We don't know for sure if that [Aircraft Z] heard and/or acknowledged that clearance. And the Ground Controller was pretty busy. We're not exactly sure if Controller repeated the clearance either. We didn't hear a repeat. (I guess we'd have to check the tapes for that.)So as per our clearance; we started to taxi out taxiway after the [Aircraft Y] passed by us. The [Aircraft Z]; coming from our left (South); just kept taxiing northbound at high speed; with no signs of slowing down. My FO queried Ground to see if the [Aircraft Z] was going to give way to us. Ground asked [Aircraft Z] that and [Aircraft Z] replied 'Negative' and just kept going. He basically cut us off. I applied heavier than normal braking to stop and we kept a safe distance from this [Aircraft Z] while he sped past us. ZZZ Ground Control could have repeated the Clearance to the [Aircraft Z] and/or made sure that [Aircraft Z] understood the first 'give way to [Aircraft X]' clearance; but the Controller was very busy. And the [Aircraft Z] pilots should have heard the first clearance; but they also should have checked with Ground Control when they saw us coming out.




Synopsis: B737 Pilot had a ground conflict with another aircraft during taxi out for takeoff.
Date: 201502
Local time of day: 0001-0600
Location: IAH.Tower, TX
Light: Night
Aircraft: Widebody; Low Wing; 4 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B IAH
ATC / advisory: Tower IAH
Second aircraft: Medium Large Transport
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Clearance
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: Aircraft X was cleared for take-off runway 15L with a right turn heading 360; the pilot read the clearance back correctly including the right turn heading 360.  Becoming airborne; he made a left turn heading 360.  Because we were arriving west; this put him in conflict with traffic arriving runway 27; specifically involving the wake turbulence from the Aircraft X. Traffic was exchanged to both the Aircraft X and the Aircraft Y arriving runway 27.  Aircraft X was instructed to expedite his climb for traffic.  The Aircraft Y arriving runway 27 was advised of the wake turbulence and the altitude of Aircraft X and was told his best course would be to continue his descent and land keeping him below the wake.  Breaking out Aircraft Y would have put him in the middle of the wake turbulence.




Synopsis: IAH Tower Controller describes a departure turning the wrong direction; into the arrival path of a smaller jet causing a wake turbulence problem.
Date: 202001
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: VMC; 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class C ZZZ
Reporter organization: FBO
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: While on downwind for Runway XX at ZZZ; I heard a twin-engine Cessna announce he was departing westbound before takeoff on Runway XX. The offending aircraft took off; then turned west before reaching pattern altitude and cut across downwind leg (Runway XX) at pattern altitude between two other aircraft. I estimate that the offending aircraft missed my aircraft by approximately 300 ft.




Synopsis: Pilot reported a near mid air collision while conducting flight training in the VFR traffic pattern.