elihoole/asrs-aviation-reports huggingface dataset:
Date: 201704
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 50
Light: Night
Aircraft: Cessna Stationair/Turbo Stationair 6
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Captain; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Ground Event / Encounter Other / Unknown
Detector: Person Gate Agent / CSR; Person Other Person
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Airport
Primary problem: Human Factors

Narrative: Returning from a cross country trip at night to ZZZ. Originally departed ZZZ in daylight. Prior to departure a training aircraft had a landing mishap resulting in a collapsed gear. The accident airplane was off the side of the runway approximately 1;500 feet from the threshold end of runway 23. The airplane was in the overrun area and clear of the runway. Many aircraft were landing and departing after the incident. We checked NOTAMs prior to our 50 minute return flight to ZZZ. When approaching ZZZ and calling our position in the traffic area we were informed by an aircraft making practice approaches that the ZZZ airport manager had the runway lights turned off and the airport was closed by NOTAM. I called approach and requested a NOTAM check for ZZZ. Approach contacted flight service and no NOTAMs where reported for ZZZ. I confirmed twice before proceeding. I flew a low approach down the runway to confirm the runway was clear. The landing incident aircraft was still sitting off the runway in the overrun safety zone. I flew another pattern and landed uneventfully and beyond the incident aircraft regardless of the runway lights being turned off by the ZZZ manager. After shutdown the airport manager blocked my aircraft and started yelling at me that the airport was closed by NOTAM. I advised him that there were no NOTAMs for ZZZ in the system. He continued to yell and state there was a NOTAM and I acted in a careless manner and could have killed someone. (No one was there other he and a line boy) I checked online again and called Flight Service after the manager left and it was confirmed a fourth time that there were no NOTAMs issued or in the system for ZZZ. I advised Flight Service that the airport manager had shut down the runway light system and was advising pilots that the airport was closed by NOTAM. The flight service specialist was very surprised and advised me that he would contact his supervisor and have him call the ZZZ manager. I went online and at the time a NOTAM was published for the runway closure at ZZZ.




Synopsis: C206 pilot reported being informed by another pilot after landing that the airport was closed and the lights were deactivated due to an aircraft incident earlier in the day.
Date: 201209
Local time of day: 0601-1200
Location: GRD.Airport, SC
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class G GRD
ATC / advisory: CTAF GRD
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Distraction; Confusion; Communication Breakdown; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Upon departing the GRD airport off of Runway 09; we (instructor and student) flew straight out and departed the pattern to the east over Lake Greenwood at 2;500 FT. We performed several maneuvers and then turned to return to GRD. My student reported our position to be 6 miles out to the east descending to 1;430 FT to enter a 45 degree left downwind for Runway 9 GRD. Another pilot reported he was 7 miles north of the field and would be entering left traffic for Runway 9. The pilot asked for our current position and we reported abeam Runway 27 entering the left downwind for Runway 9. The other pilot then reported he would extend his upwind and enter the pattern behind us. Upon each of our position reports the other pilot responded with 'oakie dokie'. The other pilot reported abeam the end of Runway 9 on his downwind. I immediately responded that our aircraft was turning base for Runway 9 with a response from the other pilot of 'oakie dokie'. We then reported turning final for Runway 9 with a response from the other aircraft of 'oakie dokie'. We were in the flare for landing on Runway 9 when the other pilot's landing gear passed overhead about 30 FT above our glare shield and he landed about 200 FT in front of us. Post flight conversation revealed he never had us in sight and 'assumed' we were clear of the runway. Contributing factors were he had three children in the airplane with him distracting his attention. Also the aircraft is a low wing plane and our aircraft is high wing therefore inhibiting sight of one another. I do not want to get the other pilot in trouble but this was an incident that was very close to an accident do to his lack of vigilance.




Synopsis: An instructor with his student landing on GRD Runway 9 reported a near miss after another aircraft passed 30 FT overhead his aircraft which was in the landing flare.
Date: 201308
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: Descent
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Altitude Hold/Capture
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Undershoot
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Took Evasive Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Had the aircraft level at 7;150 FT instead of 7;000 FT on descent. Aircraft was in VNAV.  All altimeters were correct with no splits.  I would think that this is just a glitch; but this is the third time I've had it happen in different aircraft over the last three weeks.  It happens in VNAV mode only and errors have been between 140 FT and 400 FT every time.  I don't know if there has been some sort of software update recently but again it has happened repeatedly with different first officers so I don't think that it is just me screwing up the FMC.

Callback: The reporter stated that he did not realize until the third occurrence of the early level off that this anomaly was aircraft related and not a crew error. He is now vigilant during every approach to a level off. In order to correct the early level off; the aircraft is put in a Vertical Speed Mode (VS) descent and it then levels at MCP selected altitude.



Synopsis: A B737-700 Captain noted that a series of aircraft autopilots level off between 150 FT and 400 FT early during descents in VNAV.
Date: 201302
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: Marginal
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: TRACON ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Diverted; Flight Crew Inflight Shutdown; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While on climbout we were watching our oil quantity on engine number one because it had been serviced before departure. We were topped off to 12 quarts before departure. During climbout we watched a steady drop in quantity in the same engine. Within 70 or so miles from our departure; we had dropped from 12 to 5 quarts. At this point we had begun to contact Dispatch. With a great deal of CRM we decided together that we would watch the pressure and temp of the engine. When we saw a change and [a] drop to 4 quarts we decided to divert to [a nearby suitable airport]. Being so close to [the selected airport] it was the best plan of action. With a change in indications on our ICAS we felt that the engine should be shut down to hopefully save it mechanically. Running our checklists and the QRH we shut engine one down; declared an emergency; and began to take vectors to the approach. After finishing our checklists we decided we would restart the engine as we intercepted the final approach course. At this point the engine was shut down and we read 6 quarts. We decided this because of an underlying layer of possible ice. As we intercepted we restarted engine one. Before we hit the marker the quantity had dropped to two quarts.  We landed safely on two engines and then as we taxied off the high speed we shut number one down again. The plane was taken to the hangar.




Synopsis: EMB-145LR First Officer reported number 1 engine oil quantity decreased rapidly after takeoff; noting the engine had been serviced for oil before departure. Flight crew decided to divert to nearest suitable airport; the engine was shut down during the divert; and restarted for the approach.
Date: 201510
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Trailing Edge Flap
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During final approach to ZZZ; flaps failed to extend after passing Flap Position 2. Indicator showed flaps stuck between Flap position 2 and 5 while flap handle was extended to Position 15. Go-around initiated and flap retraction to Position 1 attempted; but flaps would not move in either direction. Holding instructions were given to work problem and coordinate with Dispatch and [maintenance control]. QRH checklist followed and alternate flap extension procedure followed which allowed flap to extend to Position 15. Approximately 15 minutes were spent in holding before we were ready to initiate approach for landing. Visual approach approved to ZZZ. Weather was VMC and visibility greater than 10 nm below 10;000 ft MSL. Approach; landing and rollout was uneventful. Fire Chief inspected aircraft for possible damage or fire condition before allowing taxi to parking gate. Taxi to gate and engine shutdown/parking was also uneventful.




Synopsis: B737 Captain reported a trailing edge flap issue which limited flap extension to 15 degrees.
Date: 202110
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Initial Approach
Airspace: Class D ZZZ
Second aircraft: UAV: Unpiloted Aerial Vehicle
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Time Pressure; Distraction; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Unauthorized Flight Operations (UAS)
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: I was doing a flight with my private student and was in the traffic pattern for Runway XXL at ZZZ; on the third lap in the pattern I saw something in my peripheral vision. My student couldn't see it due to the altitude the engine cowling was blocking his vision; there was a drone that was at approximately 1;100 ft. I quickly pulled the yoke back to gain altitude to avoid the drone that was right in front of us. I reported it to the ZZZ Tower and they asked me questions about what happened; the drone activity was not a part of the ZZZ ATIS; and the Controllers did not see it. When I landed the plane I had to call the ZZZ Tower and give them a little more details and filed a safety report with my flight school.




Synopsis: Flight Instructor reported a near miss with a UAS while in the traffic pattern and took evasive action.
Date: 201604
Local time of day: 1201-1800
Location: DTW.Airport, MI
Flight conditions: VMC
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower DTW
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Confusion
Second reporter function: Pilot Flying; Captain
Anomaly: Conflict Ground Conflict; Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew Rejected Takeoff; Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: During takeoff roll [on Runway 21R]; it appeared another aircraft was crossing our runway after we were given takeoff clearance. At about 80-100 knots; the Captain elected to reject the takeoff. I was the PF. I made a radio call to the Tower to let them know we rejected. Tower asked why and I replied due to an aircraft crossing our runway. Tower replied the aircraft was on a taxiway and that it was a common occurrence. I did not ask whether it was common for aircraft to reject or just think there was an aircraft crossing. We returned to the gate for fuel and brake cooling. RTO was otherwise uneventful.


Second narrative: [Report narrative contained no additional information.]


Synopsis: B737 flight crew reported they thought an aircraft was crossing at the departure end during takeoff from DTW so the Captain elected to reject the takeoff when in actuality the other aircraft was on a perpendicular taxiway.
Date: 201706
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: Cessna 152
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear
Component problem: Failed
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Observer
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: My student got a prop strike on his first solo. My student has more than 60 hours (he changed 3 times of instructor because they got a job in the airlines). Before soloing him I covered all the part 61-87 and even sent him to pre solo with another instructor; he is a very good student and always since I started with him he did all his landing without my help. So after giving him the pre solo written test and the 3 endorsements for the solo; he took off under my supervision; did his traffic pattern and got the clearance to land full stop on; he touched down but started to bounce; at the 3 bounces the nose wheel collapsed and he finished his landing on the prop. Of course; I have taught him about going around but he was so focused on landing the airplane.




Synopsis: A flight instructor reported observing a student pilot on the first solo flight; bounce on landing resulting in a collapsed nosegear and prop strike.
Date: 201211
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: Mixed
Aircraft: B737-800
Mission: Passenger
Flight phase: Final Approach
Aircraft component: Navigational Equipment and Processing
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Landing at destination airport we did an RNAV approach. With flaps 15 at 2;000 FT the gear warning horn and configuration light and ICAS activated and to stop it we had to put the gear down as we passed 1;700 FT and with VNAV path the slope jumped to 650 FT. I leveled out the plane as this was not right. We broke out of the weather over the runway at 1;500 FT; the FMS still telling us the runway was still 2.5 miles ahead as we went over the runway now in VMC conditions. I was able to circle to the left and come in and land safely. We think we either had a map shift or a radar altimeter problem. We put it in the book and had Maintenance check it out: they found nothing. On the first sign of an abnormal situation such as the gear horn coming on when not supposed to; it should have been a clue of other things that could go bad. If this happened in mountainous terrain; I may have been more spring loaded to go around sooner. As these airplanes get older we have to be very alert to strange things. I hope we get the new planes soon.




Synopsis: B737-800 flight crew on approach received multiple aural and ICAS warning indications and elected to abandon the approach. In VMC they circled and landed without incident.
Date: 201409
Local time of day: 1201-1800
Location: LAF.Airport, IN
Light: Daylight
Aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 91
Flight plan: VFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class D LAF
ATC / advisory: Tower LAF
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Reporter organization: Government
Reporter function: Instructor; Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Training / Qualification; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I was training somebody on the Local control position.  Aircraft X was put in position for RWY 10 while Aircraft Z was landing on RWY 23.  Once Aircraft Z was through the runway intersection the trainee cleared Aircraft X for takeoff from RWY 10 with Aircraft Y on final for RWY 23.  When it became apparent for me that there was not going to be separation I by mistake told Aircraft Z to 'Go around traffic departing RWY 10' instead of Aircraft Y.  The read back was garbled; but it appeared that Aircraft Y took the go around.  My trainee also instructed Aircraft Z to go around by mistake to which Aircraft Y responded that they were going around.  I then instructed Aircraft Y to go around.  This was all complete before Aircraft Y crossed the runway threshold.  Aircraft Y then proceeded to fly toward Aircraft X taking evasive action at the last minute to miss the aircraft.  I should have had a better idea of who was the next person on final.  Based on the chips on the magnetic board we use to track aircraft; it appeared that Aircraft Z was the next person on final.  I also allowed the trainee to go to far in this circumstance.  I should not have allowed Aircraft X to depart RWY 10.  I also should have been more specific about which direction Aircraft Y should fly instead of just calling traffic after the go around was issued.




Synopsis: LAF Tower Controller while instructing observes something that isn't going to work.  He sends an aircraft around but uses the wrong (similar) call sign.  Correct aircraft goes around but turns into another aircraft on the pattern and takes evasive actions to avoid it.
Date: 202010
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
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: Pilot Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Captain; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Human Factors

Narrative: VMC approach to Runway XXR at ZZZ at night; PAPI OTS. We were cleared the visual on a right base to the FAF. We flew the approach in LNAV/VNAV and showed on glidepath as we approached the turn to final. I had gear down; flaps 15 as we rolled out and was slowing to 180 knots. We both felt we were high although the PDI indicated only slightly above glideslope. We continued to configure the aircraft and called for the landing checklist. At 500; I called 'stable' when we realized the flaps were at 25 not 30. The Captain selected flaps 30 and we continued the approach and landing without incident.This was the Captain's third flight since March; I have flown more recently but it's been 3 weeks since my most recent flight.


Second narrative: Visual approach night VMC to [Runway] XXR ZZZ.  PAPI inop. Upon accepting the visual approach from a modified right base to XXR we elected to follow the LNAV and VNAV path to the runway in visual conditions. Upon turning final we appeared to be high visually but VNAV was showing on path. We configured the aircraft rapidly; but on speed for gear down and final flaps.Upon reaching 500 feet both First Officer and I realized we were at flaps 25 not 30. I selected flaps 30 below 500 feet and we continued the approach and landing without incident.


Synopsis: Air carrier flight crew reported an unstabilized approach due to a wrong flap setting.