elihoole/asrs-aviation-reports huggingface dataset:
Date: 202009
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Landing Without Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: While we were instructed to join the Runway XXC localizer ZZZ; Approach Controller handed us over to Tower Frequency. As soon as we joined the localizer; flying conditions started to deteriorate and became turbulent. Airspeed was fluctuating at 1;400 feet AGL. As a result of this; I had started to get focused on stable approach criteria; and work load gradually increased for both pilots. Over emphasis on stable approach criteria caused a distraction and both PF and PM forgot to obtain the landing clearance. Aircraft landed without any further incidents exited the runway and hold short of XXL. Since we did not hear anything from the Tower; both pilots became aware of the event and switched to Tower Frequency. Flight was completed without further incidents.Tunnel vision on stable approach parameters and Airspeed variations caused distraction. Since COVID-19 breakout; I was not flying as frequently as before. I believe this was factored into this incident.Give some extra time to double check all the required tasks are completed. As we are not flying as frequently as before; configure the aircraft early and passing 500 feet AGL; both pilots verbally verify one last time 'Cleared to Land.'




Synopsis: Air Carrier First Officer reported landing without a clearance and stated lack of flying was a contributing factor.
Date: 201202
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Brake System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Aircraft; Chart Or Publication; Human Factors; MEL; Procedure
Primary problem: MEL

Narrative: The [flight] crew called from ZZZ and said that the #2 Hydraulic System was reading 100 percent in the 'OFF' position; but reads correct pressure when in the 'ON' position. I then deferred the #2 Hydraulic Accumulator as in the past. The aircraft flew one leg and when Maintenance went to fix it; they found there was no # 2 Accumulator installed.The Accumulator had been removed based on an Airworthiness Directive (AD). The flight crew and I were unaware that they had been removed. And the MEL did not state it. We took the aircraft off-line and fixed the problem. That same day a note was put into the MEL stating the two accumulators had been removed from the aircraft.




Synopsis: A Line Mechanic reports he deferred the #2 Hydraulic System Accumulator on a company CRJ-CL65 aircraft under their MEL procedures after the flight crew reported incorrect pressure readings. Downline Maintenance reported #2 Hydraulic Accumulator had been previously removed per an Airworthiness Directive (AD); but their MEL had not been updated.
Date: 201307
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 5
Light: Daylight
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Final Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Human factors: Confusion
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; General Declared Emergency
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: At approximately 1;200 FT; while turning final; the Number 2 Engine rolled back. The First Officer noticed immediately. I had just disconnected the autopilot; and pressed the autopilot noise cancellation button. The cancel button is located near the fuel lever. I do not know if I bumped the fuel lever off; but it is hard to figure how because the switch has a detent. We declared an emergency and landed uneventfully.


Second narrative: I was running the Landing Checklist and noticed on the right ECAM the Number 2 Engine was rolling back. I looked down and saw the Number 2 fuel lever was not in the on detent and significantly farther back than the Number 1. I told the Captain the Number 2 fuel lever was off; turned it back on momentarily to see if the engine would recover; it did not. The Captain directed me to declare an emergency which I did.


Synopsis: A300 flight crew reported while turning final the Captain inadvertently shut down Number 2 Engine while trying to cancel the autopilot disconnect warning horn.
Date: 201405
Local time of day: 1201-1800
Location: ATL.Airport, GA
Light: Daylight
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ATL
ATC / advisory: Tower ATL
Second aircraft: Medium Transport; Low Wing; 2 Turboprop Eng
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Procedure; Aircraft
Primary problem: Procedure

Narrative: I was working Local. Aircraft X was on a visual approach over DEPOT for RWY 27L when I observed Aircraft Y on base leg for RWY28 doing 250 knots and at the same altitude as Aircraft X and aimed right for him. Hard to turn final at that speed; so I was expecting him to slop through; which he did. He was right behind Aircraft X at the same altitude maybe 1 mile apart. I haven't seen the replay and I don't want to because it was scary enough seeing it once. I was reaching for the button to call Final when Aircraft X called me. I canceled his approach clearance and climbed him to 40 and told him to track the localizer. I final called me and I told him Aircraft X was climbing. I coordinated with a final for the go-around.Turn early to join the localizer or slow aircraft down before the turn.




Synopsis: ATL Tower Controller reports of high speed aircraft coming too close to another arrival and having to send first aircraft around.
Date: 201201
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Fuel Quantity-Pressure Indication
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Troubleshooting
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Conflict Airborne Conflict; Inflight Event / Encounter Fuel Issue
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Took Evasive Action; Flight Crew Landed in Emergency Condition; General Maintenance Action; General Declared Emergency
Contributing factors: Aircraft; Manuals
Primary problem: Aircraft

Narrative: After climbing out; discovered right fuel gauge and totalize 'blank.' Called Dispatch and Maintenance and agreed to land at a nearby divert airport; since we didn't know if this was the problem or a symptom of a bigger fuel problem. Was just this gauge out; or did we lose fuel from the right side also? The only gauge to show fuel was the left side approximately 9;600 LBS (that's not enough to go to our filed destination). Declared emergency and went to the divert airport. On visual approach to Runway XXL; TCAS reported an airplane off our right. This aircraft was landing on Runway XXR. The copilot was flying and had him in sight. TCAS told us to climb; which we did. Copilot always had the aircraft in sight; but since TCAS said climb; we did climb. After conflict resolved we continued on the approach and landed uneventfully. Had Maintenance determine it was just a gauge problem. Had it deferred and placard. [We] had quantity check by lowering the fuel sticks. Got new release then went to our filed destination.


Second narrative: Need some guidance in QRH for this fuel quantity indicator failure.


Synopsis: A B757 crew found the right fuel gauge and totalizer both blank and not knowing the problem declared an emergency and diverted for a maintenance examination; which determined the cause to be a gauge failure.
Date: 202101
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: FBO
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Student
Human factors: Training / Qualification
Anomaly: Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: On private lesson I took off and went to practice area and went through all maneuvers with no problems. I then flew back to the airport and did two successful landings and one takeoff. On my last takeoff I was preparing to do a short field takeoff. I rolled onto [the] runway with the yoke all the way back once getting lined up with the center of the runway I put in full power and started my takeoff. As I was rolling down the runway I added right rudder to keep down the center line. The plane left the ground and instantly turned to the left. I tried adding more right rudder to get the plane going straight. The plane continued to go to the left as it gained altitude. After I felt the plane was not going to recover I tried to put the plane down as softly as possible in the field left of the runway. I touched down in the field and rolled to a stop. I then went through engine shutdown procedure to turn the plane off. After the plane was turned off I waited for help and got out of the plane.




Synopsis: PA-28 student pilot reported landing in a field after having directional control difficulties while attempting a practice short field takeoff.
Date: 201909
Local time of day: 0001-0600
Location: LMO.Airport, CO
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operating under: Part 91
Flight phase: Final Approach
Airspace: Class E ZDV
Reporter organization: Contracted Service
Reporter function: skydiver
Reporter qualification: Other USPA-B
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Airspace Violation All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Observer
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure; Airspace Structure
Primary problem: Human Factors

Narrative: I was directly over the southern edge of the skydiving drop zone at LMO; under canopy and about 1;000 ft. AGL when a light; low-wing aircraft flew directly over my canopy missing me by no more than 400 ft. I did not see the aircraft until it passed me as both of us were facing the same direction. The aircraft was overflying the airport. On the ground some of my fellow skydivers made comments such as 'how does it feel to be buzzed by an airplane?' LMO AWOS has a statement at the end of each report requesting no airport overflights while skydiving is in progress. I don't know if the aircraft landed at LMO. Skydiving activity is clearly marked on sectional and TAC charts. About six months ago one of my skydiving buddies and her student had a light aircraft fly between them while they were setting up their landing patterns.




Synopsis: Skydiver reported that an aircraft violated published procedure; resulting in an NMAC.
Date: 201708
Local time of day: 0601-1200
Location: HAF.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class B SFO
ATC / advisory: TRACON NCT
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Airspace Violation All Types
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I filed IFR direct to OSI VOR then direct destination per the departure procedure for Runway 12. At takeoff the winds were 310 at 6-8 knots. Since it was VFR I elected to takeoff on Runway 30 and we were at full fuel and within 150 pounds of gross weight.There is a local noise restriction in this direction requiring a climb of 500 feet before turning and right traffic toward the hills running parallel to the runway.Passing 500 feet I started the right turn and immediately knew I had made a mistake. I did not feel comfortable with the turn to come up short of the hills nor was I sure I would be high enough to adequately clear the tops or any obstruction. I froze for a moment then called NorCal with my position and to start IFR flight plan. They gave me a squawk code and informed me of Bravo intrusion.Without the hills and the unknown of obstructions the turn was doable. I was alternately heads down looking at the graphical depiction of the airspace during the process which contributed to my delayed responses and decision making.I did not make any extreme maneuvers to avoid the Bravo rather I called NorCal. A downwind take off was technically doable; but I thought the conditions favored the upwind choice. I was mistaken. Delaying the flight was also an option although weather along my route was changing.I searched the AFD and other sources for comments about Runway 30 at HAF prior to takeoff; but did not see anything that aroused my suspicion. The only airport signs I saw were concerning the noise restrictions although the sign posted at the runway was faded and hard to read.




Synopsis: GA pilot reported a Bravo airspace intrusion on departure from HAF due to an aircraft close to max gross weight and terrain considerations.
Date: 202002
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-32 Cherokee Six/Lance/Saratoga/6X
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: CTAF ZZZ
Second aircraft: Small Aircraft
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft was being taxied for intersection departure. After making taxi and departure intersection calls; Pilot in Command looked to ensure there was no traffic on short final prior to departing. Another aircraft called the callsign of the taxiing aircraft just as they were about to pass on landing. Taxiing aircraft stopped just as landing aircraft passed during rotation.




Synopsis: An Air Taxi pilot about to enter the runway from an intersection at a non towered airport reported a landing aircraft notified them just as they were passing the intersection.
Date: 201408
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The Number 1 Engine failed at approximately FL230. Declared an emergency with ATC and returned to departure airport for landing (single engine and overweight). Normal landing and taxi to get gate after ARFF personnel checked for fire.


Second narrative: Normal pre-flight; taxi and takeoff. Passing about FL220; left engine failed. Engine Fail Light illuminated; yaw and engine 'winding down' noise. First Officer was pilot flying. Autopilot B Engaged. Captain applied initial rudder and then re-assigned me to keep flying while he declared an emergency and started the APU. I leveled; turned towards the nearest field and then started a descent to 15;000. Captain queried ATC as to available runway and length. 6;000 FT was the answer and that seemed unnecessary given our altitude and proximity to the departure airport as we were 145K for landing. Engine Failure Checklist; QRH expanded Engine Failure Checklist; Emergency Landing; and Single Engine Landing Checklist all accomplished as well as diversion report and code 7700 via ACARS. Flight attendants received their TEST brief. We routed direct in a steady and constant descent to setup for a left base for the longest runway. We had to route just west of direct due to thunderstorms. Descent and Landing checklists completed and landed flaps 15 and about 145 KTS. [We] rolled out to the end with minimal braking. The Fire Chief scanned left engine and brakes. No heat returns for either. We taxied to the gate and consulted Brake Cooling Chart during taxi in simply for situational awareness as we had confirmation of no overheat from ARFF. Equipment (pallet loader/dolly) over red line. Equipment moved and we taxied in to gate. Maintenance met us and said that the hot section appeared to have come apart. First Officer went to look for a stroller for a passenger and observed metal fragments under tail pipe. Appeared to be contained minus what exited out of the aft turbine section and tail pipe. Oil remained fully serviced throughout. Captain made log entries for Engine Failure and Overweight Landing.


Synopsis: B737-800 flight crew experiences an engine failure passing FL220 during climb. The engine is secured and the flight returns to the departure airport for an overweight landing.
Date: 201206
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Air Carrier
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Situational Awareness; Distraction; Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Maintenance Action; General Declared Emergency
Contributing factors: Aircraft; Procedure
Primary problem: Procedure

Narrative: I departed in a CE525 single pilot with no passengers. I was bringing the airplane back to our home base. Climbing through FL300 the low oil pressure light came on. I confirmed it by checking the oil pressure gauge. I notified Center of the situation and declared emergency. I requested a turn back to the departure airport and a descent in order to shut down the engine. On the descent; I followed the checklist procedures and shut down the engine. My initial intent was to go back to my departure airport but I was right over a large suitable airport and decided that would be a better choice. I landed single engine with no issues. Upon landing; I checked the oil level on the engine and there was none in the sight glass. When I departed; the oil level was midway between the full and add line. There was oil running outside the cowling. The Maintenance Department was notified and they sent two mechanics. The mechanics replaced a seal on the starter generator; which seemed like the location of the leak. The next day; I departed enroute to home base. Upon leveling at FL330; I noticed the same engine oil pressure gauge gradually decreasing. I notified the Center Controller of the situation and requested a return to departure airport which was 100 nautical miles away. On my descent; the low oil pressure light came on again on the same engine. I followed the checklist procedures and shut down the same engine again. I landed back at the departure airport. The same Mechanics went back to work on the engine. They were unable to find exactly where the oil was leaking from but they were told then to replace every possible component that could cause that issue. After that; I test flew the airplane and no more issues.




Synopsis: A CE-525 pilot shut the same engine down on two consecutive flight and diverted after low oil pressure warnings from oil loss. Eventually; all accessories were replaced and the ferry flight completed.