elihoole/asrs-aviation-reports huggingface dataset:
Date: 201909
Local time of day: 1201-1800
Location: BWI.Tower, MD
Flight conditions: VMC
Weather elements / visibility: Turbulence; 10
Light: Daylight
Aircraft: Cessna 150
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class B BWI
ATC / advisory: TRACON PCT
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Training / Qualification; Workload
Anomaly: Airspace Violation All Types; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Exited Penetrated Airspace
Contributing factors: Weather
Primary problem: Weather

Narrative: Enroute from SFRA Paleo Gate to Tipton Airport FME; at 1400 ft. MSL; below the 1500 ft. BWI Bravo floor.  Turbulence increased significantly enroute from the shoreline to FME and caused my aircraft to briefly ascend into Bravo airspace and back down.  Potomac [Approach] contacted me on 132.77 and indicated that I had popped up into the Bravo and back down.  I apologized.  The Controller indicated it he understood; but advised me to remain clear of the Bravo. My altimeter setting was consistent with the setting I received on entering the Paleo Gate.  I believe it was 30.11.  I descended to 1300 ft. MSL to avoid repeating the incident. I continued the flight to FME and landed without further incident.




Synopsis: Cessna 150 Student Pilot reported Class B airspace violation due to turbulence.
Date: 201304
Local time of day: 0601-1200
Location: ZZZ.Airport, US
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
Second aircraft: B757-200
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical; 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 Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition; Flight Crew Diverted; Flight Crew Landed As Precaution; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After leveling at FL300; Flight Attendant contacted cockpit via inter-phone to report strong electrical fumes in the vicinity of the mid galley. First Officer was PF. I delegated aircraft control and radios to him; and I consulted QRH. The checklist was accomplished down to 'Depowering IFE'; 'Utility Buses'; and 'Recirc Fans.' A short time later the Flight Attendant reported back that the fumes became stronger. An emergency was declared and an immediate divert initiated. I requested that ATC notify the company due to task saturation and proximity to landing airport. We landed safely overweight at 203;500. Passengers were deplaned and ARFF began their investigation. All pertinent logbook entries accomplished.


Second narrative: [This report contains no additional information.]


Synopsis: The flight crew of a Boeing 757-200 was notified by a Flight Attendant 10 minutes after level off of a metal/electrical burning odor mainly in the center galley area of the cabin and the condition was worsening. An Emergency was declared and the aircraft diverted to a near by airport; and landed over-weight without incident.
Date: 201206
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: MD-82
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: Pneumatic Ducting
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After takeoff at approximately 1;400 FT; a Master Warning and tail compartment temperature high warning light was observed. We accomplished the memory action items and declared an emergency. We advised ATC that we would like to return to [departure airport] for a landing. We completed checklist items and returned for an overweight landing. Our landing weight was 133;000 lbs. The emergency fire trucks checked the tail compartment area for heat and advised us that the only detectable heat was coming from the engines. We returned to the gate and deplaned the passengers.


Second narrative: [Narrative 2 had no additional information]


Synopsis: MD-82 flight crew reported TAIL COMP TEMP HIGH light shortly after takeoff. They ran the procedure; declared and emergency; and returned to departure airport.
Date: 201708
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: Rain; 10
Light: Daylight
Aircraft: PA-32 Cherokee Six/Lance/Saratoga/6X
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Throttle/Power Lever
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Captain; Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Distraction
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was flying a direct IFR route to ZZZ. ATC instructed to descend and maintain 4500 feet. When I adjusted the throttle; the Manifold Absolute Pressure (MAP) decreased to 12 and I lost power to the aircraft. The engine was still running although at very low idle with no ability to move the throttle lever. I immediately informed ATC and diverted towards [the nearest] airport. I was still approximately 12 miles away and began the failed engine checklist with intentions of landing on a straight roadway. Upon pitching for best glide; I went through the failed engine checklist to notice the throttle was stuck. I manually forced the throttle forward and the plane immediately responded with full MAP. Seeing that the aircraft had restored full power; I then redirected back to my original destination without further incident. I landed safely and informed ATC of my arrival.




Synopsis: PA32 pilot reported experiencing a loss of engine power when the throttle was reduced for descent. The throttle appeared stuck but the reporter was able to force it and restore engine power.
Date: 201208
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Light: Night
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Reporter organization: Air Carrier
Reporter function: First Officer
Human factors: Situational Awareness; Physiological - Other; Fatigue
Anomaly: Other Fatigue
Detector: Person Flight Crew
When detected: Pre-flight
Result: Flight Crew Became Reoriented; General Work Refused
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: [I] called in fatigued for a field standby. [I] had just flown a 2 day trip; early departure both days. The layover on the West Coast resulted in very limited sleep. I slept possibly 3 hours. Two major factors affected my sleep that night. One was the air conditioning system; it would not keep the fan running as programmed. Every time it turned on it 'clunked.' Also had neighbors who routinely entered and exited their room several times until just before my wake up time. They were also extremely noisy. I tried to compensate by wearing ear plugs for both issues; but the end result was still no sleep. The next morning I compensated for fatigue with coffee. I had a 3 hour 28 minute layover at the first destination. But due to the coffee and substandard rest facilities in our operations area; I was unable to get any rest with a nap. I completed the trip and went home. Shortly after arriving home and right before bed I was contacted for a late morning field standby on what would be my day of duty. After the assignment I made the preparations for driving back to the airport in the morning. That night I was still wound up from the coffee I had during the day (I don't normally drink coffee) and had trouble unwinding. After about 3 total hours of fitful sleeping I made the decision to call in fatigued just before morning twilight.




Synopsis: An A320 First Officer called in fatigued for airport standby on his third duty day because on the previous two nights he was not able to get fitful rest.
Date: 201904
Local time of day: 1201-1800
Location: APA.Airport, CO
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class D APA
ATC / advisory: Tower APA
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: [Took] off on Runway 17L to join the right hand pattern for touch and goes on 17R. Tower let me know that there was a plane in the pattern above and to my right - I saw a plane turning towards the downwind; so I waited until he was no factor and turned till I was also on the downwind.Tower asked me to do s-turns in the pattern (I'm assuming for distancing). A little less than midway; someone made a radio call asking about the plane above them. While in a slight westerly s-turn; I looked down and saw a Cessna at 10-11 o'clock about 150 feet horizontal and 75 feet vertical flying the same direction I was.Naturally; I turned easterly and slowed down; keeping my eyes on this plane the whole time. He went west and boosted his speed; until he was much further ahead of me.I don't know [if] he was behind the plane I saw and I cut him off by turning for the crosswind too early or if he was entering the pattern at the mid-field downwind and got really close. Tower made no mention of our distancing.




Synopsis: C172 pilot reported a NMAC in the pattern at APA airport.
Date: 201709
Local time of day: 1801-2400
Location: CZQX.ARTCC, NF
Flight conditions: VMC
Light: Night
Aircraft: B747 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
ATC / advisory: Center CZQX
Aircraft component: FMS/FMC
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not 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: After entering Class II airspace after radar service terminated we had a dual FMC failure. I immediately went back to the last VHF frequency we were working and the Controller still had us on radar. We entered a holding pattern and completed the QRC. We did not pull and reset the CB as was optional in the checklist. Right FMC recovered after about 5 minutes. The left FMC did not recover. We coordinated with [Dispatch; Maintenance; and Operation] and passenger advocacy. We all agreed the best course of action was to continue to destination.




Synopsis: B747 Captain reported continuing to the destination after experiencing dual FMC failure. One FMC was successfully recovered.
Date: 202009
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: TBM 900 / TBM 930
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Navigational Equipment and Processing
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Instrument
Human factors: Human-Machine Interface; Distraction; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Aircraft; Human Factors; Weather
Primary problem: Aircraft

Narrative: Attempted to load approach into Garmin 3000 touchscreen controller. Slight turbulence caused pilot to touch load/activate button. This single action changes navigation mode; auto pilot guidance; and flight plan screen. Several pilot actions are required to undo the situation; allowing aircraft to leave the designed STAR until either reverting to manual control or completing to navigation system corrections. Perhaps a function that undoes the last command would be valuable.




Synopsis: Pilot reported turbulence caused them to activate the wrong button on their Garmin 3000 navigation screen which caused them to lose their current navigation modes and flight plan screen.
Date: 201407
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Wheel Assemblies
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Not Flying; Check Pilot; Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical; Ground Excursion Runway; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While performing a flight review with a private pilot; on touchdown after the second landing the left wheel became locked; causing the plane to veer off the runway into the grass. After inspecting the plane; it appeared that the wheel fairing had come loose and caused the wheel to lock. At the time; the private pilot was acting as pilot in command and was in control of the aircraft.




Synopsis: Instructor; performing a flight review; reports a runway excursion during landing when the left wheel fairing comes loose and locks the wheel.
Date: 201908
Local time of day: 1801-2400
Location: NCT.TRACON, CA
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class E NCT
ATC / advisory: TRACON NCT
Reporter organization: Government
Reporter function: Approach
Human factors: Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X was a VFR looking for an IFR clearance into MRY. I attempted to clear him unfortunately the pilot had issues with the read back so I cleared him with a slower pace. That gaffe clued me into the possibility they might not be as proficient as they would like. When I noticed they were below the MVA I canceled their approach clearance and proceeded to climb them.I should have issued a low altitude alert first before canceling the clearance and climbing the aircraft.




Synopsis: NorCal TRACON Controller reported a communication problem with a pilot; and then realized the aircraft was below the MVA.
Date: 201203
Local time of day: 1201-1800
Location: BHM.TRACON, AL
Flight conditions: Mixed
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Government
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class E BHM
ATC / advisory: TRACON BHM
Second aircraft: Sail Plane
Reporter organization: Government
Reporter function: Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Weather; Human Factors
Primary problem: Human Factors

Narrative: While in cruise flight at 7;000 MSL immediately after exiting a cloud; I observed a glider descending into my altitude in a slight left bank and then roll out on the same heading as my aircraft. When I first spotted the glider; I was approximately 600 to 1;000 FT behind and slightly to the right of it. He was moving slowly.I was rapidly gaining on him and within seconds of a collision. I disconnected the autopilot and entered a hard right bank trying to maintain a visual on the glider as I did not know if he had seen me or what his next maneuver would be. As I rolled out past him; I realized we had missed colliding by approximately 200 FT.The main reason this incident occurred was the pilot of the glider's lack of maintaining VFR. The glider was 'dancing with the clouds' and had likely been in the clouds at some point. At the time I spotted him; he was clear of the cloud but was not maintaining required VFR cloud separation distances. Had I been distracted for any reason or been in a faster aircraft; a collision could have occurred that would have probably resulted in the deaths of all involved and potential injury or death to others on the ground.ATC advised they did not have radar contact on the glider. Additionally; there were no NOTAMs filed indicating glider activity at the SCD airport. The AFD does indicate that glider towing operations exist on weekends in a 3 mile radius of the airport below 6;000 FT. ATC was not aware of any glider activities at the airport at the time of occurrence.Had a NOTAM been filed; ATC would have likely vectored me away from the area but the main problem here was the glider pilot's lack of adherence to the rules and safe operation.




Synopsis: As he exited clouds on an IFR flight a C182T pilot experienced an NMAC with a sailplane operating in close proximity to the cloud cover. The reporter believed the sailplane pilot to have been in violation of required VFR separation from the cloud system.
Date: 202008
Local time of day: 0601-1200
Location: GXY.Airport, CO
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class E GXY
ATC / advisory: CTAF GXY
Second aircraft: TBM 700/TBM 850
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness; Distraction; Confusion; Communication Breakdown; Training / Qualification
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: Other Take Off
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Environment - Non Weather Related; Procedure; Human Factors
Primary problem: Human Factors

Narrative: I was taking off Runway 10. Another aircraft did a low approach on Runway 35 and was clear of Runway 10 as I started my takeoff roll. I made my radio call for takeoff on Runway 10. Shortly after takeoff; I see a TBM ahead and to the right of me; on short final for Runway 35. I was able to stay low and well clear; passing underneath the TBM that did a low pass on Runway 35. There is enough space for simultaneous operations of Runway 10 and Runway 35 but I expected to pass OVER landing traffic on Rwy 35 and in this case found myself UNDER traffic that was doing a low pass. I made two errors. I thought the first plane was the one doing the lowpass (announced). When I cleared to the south prior to takeoff; I was focussed on the first plane and did not look long enough to see the TBM approaching behind him. I don't think smoke played a part in my missing the second aircraft. I think the TBM was moving quicker than expected.There were many IFR HOLDS and missed approaches being performed to the south. I think the addition of the low passes added complication to the IFR and VFR traffic in the area and would have been better avoided. I did a fullstop taxi back because I was not comfortable fitting a touch-and-go into the traffic.




Synopsis: General Aviation pilot departing from a Non Towered airport reported a NMAC with an aircraft conducting a low approach on an intersecting runway.
Date: 201308
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Aircraft: Dash 8-100
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: Center ZZZ
Aircraft component: Powerplant Lubrication System
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During the climbout the #1 ENG OIL PRESSURE warning light illuminated. We shut down the #1 Engine and returned for a landing at the departure airport. We taxied to the gate and deplaned with no further incidents.


Second narrative: [The report contains no additional information.]


Synopsis: A DHC-8-100 #1 engine LOW OIL PRESSURE alerted during climbout so the engine was shutdown; an emergency declared; and the flight returned to the departure airport.