elihoole/asrs-aviation-reports huggingface dataset:
Date: 201412
Local time of day: 0001-0600
Location: ORD.Tower, IL
Light: Night
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ORD
ATC / advisory: Tower ORD
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: We were cleared to land 28R by Tower on an 8 mile final. On short approach (800 ft); tower cleared a cargo to 'Line Up and Wait'; 28R. I could not see the traffic and did not know where the cargo aircraft currently was. I decided to initiate a go-around on the side of Safety.Tower should never give 'Takeoff' or 'Line Up and Wait' instructions to a departing aircraft; until the landing traffic has landed and cleared the point of the runway that the departing aircraft is holding short. This hazardous clearance from Tower; could lead to an aircraft landing on top of another.




Synopsis: Pilot reports being on short final when the Tower Controller put an aircraft into position on the same runway. Pilot elects to execute a go-around.
Date: 201206
Local time of day: 1201-1800
Location: LNS.Airport, PA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Approach
Airspace: Class D LNS
ATC / advisory: Tower LNS
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Communication Breakdown; Confusion; Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: IFR flight to LNS under VMC [I was] vectored by Harrisburg approach for right downwind for Runway 26 LNS. [I was] cleared for landing on Runway 26 by LNS Tower. Descending into base leg for landing; and saw other traffic; a high-wing Cessna climbing at same horizontal distance from runway; probably within 300 FT vertical separation. LNS has radar; I was never alerted to this traffic. After traffic passed over me; I heard the other traffic announce to Tower that they had passed me. I feel that Tower should have vectored the other traffic away from the arrival end of the runway; and alerted me to their presence.




Synopsis: An IFR pilot descending through 2;000 FT into LNS had a near miss with a departing aircraft but was never alerted about its presence until he saw it pass within 300 FT.
Date: 201601
Local time of day: 1201-1800
Location: ABE.Airport, PA
Flight conditions: VMC
Weather elements / visibility: Turbulence; Gusty Wind; 10
Light: Daylight
Aircraft: M-20 Series Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ABE
Second aircraft: Beechcraft King Air Undifferentiated or Other Model
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: I was on a training mission to complete a flight review and IPC on this gusty windy day. Winds were 340/11G21. We were completing the last instrument approach as part of the IPC and finishing up for the day; planning to land full stop out of the ILS 6 at ABE. The distance from the runway end to the intersection with Runway 31 is not much more (possibly less than) 2;000 feet. During the approach we were given no Land and Hold Short (LAHSO) instruction; and had one been given I would have declined it as landing out of an ILS to minimums can require significant runway; very often requiring crossing Runway 31. The landing was challenging due to the gusty winds; and after landing and during rollout I was given a 'Hold Short of Runway 31 - landing traffic' instruction approximately 500 feet from Runway 31. As I looked to my right there was a King Air that rotated and was about to touch down on 31; and had we not been able to stop (or had to execute a late go-around); there could have been a serious incident. The controller clearly put himself in a bad situation and did not take steps to correct it in a timely manner.Fortunately the strong gusty winds that day allowed for a very short rollout in the Mooney and we were able to stop and make a turn prior to Runway 31; which is usually not the case when flying that approach.




Synopsis: Mooney pilot reported a ground conflict after landing at ABE. Reporter stated this could have developed into a dangerous situation.
Date: 201306
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-32 Cherokee Six/Lance/Saratoga/6X
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Distraction; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Took Evasive Action; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On level out going to practice area; the engine began to hiccup/surge and then loose partial power; I notified Tower of my intent to land immediately; and was cleared. The power loss was momentary at that time. It occurred again; and I declared an emergency to get on the ground as soon as possible. Tower asked the questions re souls aboard and fuel; which I answered. They also asked if I wanted to have them roll equipment. I was still developing power; and could make the field and so I declined the equipment rollout. Power hiccup/surge occurred a third time on descent; but we never lost power completely. On touchdown; Tower indicated 'good Job' and on taxi; Tower asked; 'are you canceling the emergency.' I responded yes. I taxied to my Mechanic's hangar and now await word on why the power surge happened.




Synopsis: After takeoff; a PA32R engine began surging then partially loosing power; so the pilot declared an emergency and returned to the departure airport with engine still developing power.
Date: 201809
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: VFR
Mission: Photo Shoot / Video
Airspace: Class D ZZZ
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Commercial
Human factors: Confusion
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Other Person
When detected: Other after flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Looked at airspace on the morning and saw Temporary flight restrictions and was notified the temporary restriction was removed early that morning. Later when flights were reviewed it appears I penetrated controlled airspace in my inspection without prior authorization. In review with drone coordinator; it appears I confused the TFR with the Class D Controlled Airspace for ZZZ. I have updated my airspace software to prevent from future incursions.




Synopsis: Drone operator reported penetrating Class D airspace.
Date: 202008
Local time of day: 1201-1800
Flight conditions: VMC
Light: Daylight
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Corporate
Operating under: Other 107
Flight plan: None
Mission: Other Inspection
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial
Anomaly: Conflict Airborne Conflict
Detector: Person Ground Personnel; Person Other Person
When detected: In-flight; Routine Inspection
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During a UAV structure inspection; a Crop duster passed well away from the inspection. No evasive action was taken due to the UAV's close proximity to structure.




Synopsis: UAV Operator reported an airborne conflict during routine inspection with a Crop Duster.
Date: 201304
Location: ZZZ.ARTCC, US
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Cockpit Door
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty); Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Confusion; Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew FLC Overrode Automation; Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During approximately the last hour of the flight the cockpit requested a restroom break. I went into the cockpit and the Captain had trouble getting the door to open but with the help of the First Officer it opened. When I tried to open it for the Captain to come back in there was trouble again it seemed jammed. With the help of the First Officer I was able to get it open. The First Officer then tried to get out to go to the restroom and the door would not budge. The Captain then called the other flight attendants and I then took the jumpseat in the cockpit for the landing. Once we landed the door opened with no problem.




Synopsis: An A319 Flight Attendant entered the cockpit for the Captain's restroom break and the door jammed requiring two people to open it. The Flight Attendant remained in the cockpit for landing after which the door operated normally.
Date: 201911
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: Cessna 402/402C/B379 Businessliner/Utiliner
Operator: Air Taxi
Operating under: Part 135
Mission: Passenger
Flight phase: Descent
ATC / advisory: Center ZZZ
Aircraft component: Wing Flight Control Surface
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon descent 15-20 miles from the ZZZZZ for arrival into ZZZ; I felt an un-commanded left wing down force upon the aircraft. I corrected by rolling wings level and looked at the wing and noticed the sheet metal had de-laminated on the inboard forward portion of the left aileron. I conducted a control check and the aircraft responded correctly with control inputs with a bit of extra right aileron force needed to keep the wings level. I continued to ZZZ and landed uneventfully. [The cause was the] age of aircraft or an improper bonding of the sheet metal to the surface underneath.




Synopsis: C402C Captain reported an uncommanded left wing down-force due to a delamination of a portion of the left aileron skin sheet metal.
Date: 202005
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Workload; Training / Qualification; Situational Awareness; Communication Breakdown
Second reporter function: Technician
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Company Policy; Manuals; Procedure
Primary problem: Procedure

Narrative: At the start of my shift today myself and other AMT's were assigned an aircraft to put back in service and given training with threat of being disciplined if the training wasn't complete. This type of guidance is confusing in how one should go about prioritizing one's work.


Second narrative: At the start of shift on [date]; I was given a training due notification and told to have all modules completed before end of the shift or I would be disciplined. I was also given a job assignment to assist in getting Aircraft X back in service. When ask what took precedence I was told the aircraft; and felt conflicted with 2 job assignments and the threat of possible discipline.


Synopsis: Technicians reported confusion over training related to prioritization of work requirements.
Date: 202106
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: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class E ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was conducting an intro flight in Aircraft X. We had begun our take off roll and got to rotation speed; the aircraft left the ground and was slow to climb. I was pitched at about 10 to 12 degrees.The aircraft then had a reduction in power about 75 ft. off the ground before the engine surged back into full power. Once realizing that we were not going to have sufficient power to maintain the climb I immediately pulled the power back to idle and landed on the remaining runway. Air speed was approximately 95 kts. We landed with about 300 ft. remaining which resulted in a runway excursion of approximately 5 ft. There was no damage to the aircraft or airfield lighting. I taxied the aircraft back to the ramp and was able to shut down; no further incidents.




Synopsis: Pilot reported aborting takeoff at 75 feet AGL after engine power loss and landing on remaining runway.
Date: 201405
Local time of day: 1201-1800
Location: ORD.Airport, IL
Flight conditions: VMC
Light: Daylight
Aircraft: Citation V/Ultra/Encore (C560)
Operator: Fractional
Operating under: Part 135
Mission: Passenger
Flight phase: Landing
Airspace: Class B ORD
ATC / advisory: Tower ORD
Second aircraft: A340
Reporter organization: Fractional
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: Wake turbulence encounter close to ground. We were following an Airbus A340 to [Runway] 10C at O'Hare. I told the Captain that I was going to hand fly the aircraft and stay a dot to two dots high due to the aircraft in front of us. We were at 300 FT AGL and about two dots high on VGLI when the airplane started to pitch down and rapidly roll to the left. I was holding the yoke in my right hand and immediately grabbed it with my left hand to apply right aileron to counter the roll. It took me three tries to disconnect the yaw damper. I had to ask the Captain to 'help' push the throttles forward as my hands were full. We executed a successful go-around. We were high intentionally to avoid the wake but we hit it anyway. Possibly the [A340] was above the glide path as well. We maintained our assigned speed to keep our distance; and did not slow further as there was traffic behind us. Little jets don't fit in at major airports; plain and simple.




Synopsis: A CE560 First Officer encountered wake vortices from an A340 while landing at ORD.
Date: 201707
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff; Flight Crew Returned To Gate
Contributing factors: Aircraft; Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: After an uneventful taxi out to runway 30; we were cleared for takeoff. After completing the appropriate checklist; I pushed the power levers into the takeoff detent. As we started to roll; I checked the rudder pedals for authority and found that they were jammed. I retarded the throttles and slowed the aircraft to taxi speed. The Pilot Monitoring notified the tower that we were aborting the takeoff and needed to taxi clear of the runway. After exiting the runway and completing the after landing checklist I stopped the aircraft. I looked down and saw that there was a hose and small nozzle blocking the rudder pedals. We taxied back to the gate; entered the discrepancy in the log book and waited for maintenance to come to the aircraft. They found the issue and repaired it. No further issue was found.




Synopsis: EMB-145 Captain reported rejecting takeoff due to jammed rudder pedals. Taxied back to gate for maintenance corrective action.
Date: 201912
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Lancair Columbia
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Test Flight / Demonstration
Flight phase: Initial Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ; Tower ZZZ
Aircraft component: Door
Component problem: Improperly Operated; Failed
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Instrument
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: I was giving a demonstration flight to a person who had never flown a Columbia 400. The person was in the left seat; I was in the right. I showed him how to latch the door; and during the taxi and run-up I never saw a 'door open' annunciation on the panel; which should show up when any of the aircraft's doors are not latched. The person said his door was closed and latched; and he even tugged on it for security. I should have visually checked that the door was secure. We took off and were climbing out about a mile or so from the departure end of the runway; heading west; when suddenly the left door opened and completely detached from the airplane. I took control immediately and told the Departure Controller that we lost the door and needed to return to the airport with priority. The Controller switched me back to Tower and we landed uneventfully. I later went up in another airplane with a coworker and searched the area briefly for the door; and then drove in the area looking for it as well; but was unsuccessful.




Synopsis: Columbia 400 pilot reported that a cabin door detached from the aircraft on takeoff; resulting in a return to land.
Date: 201907
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Broken Clouds; 9
Light: Daylight
Aircraft: PA-32 Cherokee Six/Lance/Saratoga/6X
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness; Training / Qualification
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: General Police / Security Involved
Contributing factors: Human Factors; Airspace Structure
Primary problem: Human Factors

Narrative: Departed to ZZZ. Flight conditions were clear and calm. Upon arrival to into Class B airspace; Approach Control was very busy. We had multiple heading turns and a descent down to 1500 feet. We were unfamiliar with the airport ZZZ and ATC cancelled flight following. At this time we were over the airport and not aware of our position which was the wrong airport. My student pilot and I spotted the runway and continued to approach and land. The runway we landed on was 22 the runway we were supposed to land on was 23... which was ZZZ1 Air Force Base. I realized as soon as we landed that we were at the wrong airport. The Tower and the Base was closed on Sunday but we did have security meet us. We were detained and fined $250. We were assured this happens often but do not plan on it happening to us again.




Synopsis: PA32 Flight Instructor reported misidentifying landing runway resulting in unauthorized landing at military base.