jmbaute Posted January 28, 2018 Report Posted January 28, 2018 I wanted to learn a new data analysis tool (Power BI) so I decided to build a simple dashboard based on the NTSB database. I thought it might be interesting to the Mooney community so I am sharing the link with you. This is the same data you'll find in lots of other places, but hopefully this visualization makes it easy to slice & dice. I'm working on some other similar ones that include the GA fleet at large and one that is focused on Van's RV aircraft (GA is here and Van's is here if you're curious).A couple notes:- The data source is the XML file on the NTSB site. They update the data once per day. At this time I'm not sure if the link I'm posting refreshes against that data or if I have to trigger that refresh on my side.- The report is fairly interactive, for example click on the model donut to filter the heat map and grid. Same thing on the heat map, click to filter by phase of flight. Click again to clear your filter. - Right clicking various objects gives you a few more filtering options including raw data.- If you click any of the links to the final report and don't get a result, it is because there isn't one issued yet. I'm just building that URL based on the accident number.- I'm certainly open to feedback/suggestions but this is just something I'm playing with so I can't promise I'll do anything else with it. I am hoping to publish some other variations at a later date.- I don't care if you share the link.- If a moderator wishes to move or delete this post, I'm fine with that, too. I hope this is educational. Blue skies. John 4 2
carusoam Posted January 28, 2018 Report Posted January 28, 2018 Hey John... I clicked on the M20R on the pie chart... but got a few Bravo responses... Any ideas? I really like the idea, the ease of use, and the knowledge gained... I really like not being on the list. Best regards, -a- 1 1
mike_elliott Posted January 28, 2018 Report Posted January 28, 2018 Neat concept John. I noticed the data doesnt include one accident I am intimately familiar with, however. How accurate is your harvest of the DB?
neilpilot Posted January 28, 2018 Report Posted January 28, 2018 8 minutes ago, mike_elliott said: Neat concept John. I noticed the data doesnt include one accident I am intimately familiar with, however. How accurate is your harvest of the DB? An aircraft other than N72FG, which is in the data?
mike_elliott Posted January 28, 2018 Report Posted January 28, 2018 5 minutes ago, neilpilot said: An aircraft other than N72FG, which is in the data? I must have missed it not using the M20M filter. I do have to agree with them, the damage was "substantial" to say the least.
kris_adams Posted January 28, 2018 Report Posted January 28, 2018 15 minutes ago, mike_elliott said: Neat concept John. I noticed the data doesnt include one accident I am intimately familiar with, however. How accurate is your harvest of the DB? Same here. I was looking for a departure accident, but that was from quite a long time ago. I enjoy looking through it btw!
jmbaute Posted January 28, 2018 Author Report Posted January 28, 2018 So, the model data is human entered so there is not any consistency to the pattern they use. Sometimes it is M20R, M20-R, etc. I have a script that attempts to normalize this. I'll have to check why some of them are getting mixed in. As for the missing aircraft, I'm not sure on that one. The data is current at least of as Friday. Might be something with the make or model pattern. I'll look into it later and reply back. Thanks for the feedback. 1
warren.huisman Posted January 28, 2018 Report Posted January 28, 2018 I find it interesting that the 2nd highest accident rates occurred at cruise. Generally, this is considered a pretty safe phase of flight. Any ideas what are the common causes during this phase? Fuel shortage perhaps?
jmbaute Posted January 28, 2018 Author Report Posted January 28, 2018 3 hours ago, mike_elliott said: Neat concept John. I noticed the data doesnt include one accident I am intimately familiar with, however. How accurate is your harvest of the DB? Can you tell me a tail number of the missing plane? I will investigate against source.
jmbaute Posted January 28, 2018 Author Report Posted January 28, 2018 3 hours ago, carusoam said: Hey John... I clicked on the M20R on the pie chart... but got a few Bravo responses... Any ideas? I really like the idea, the ease of use, and the knowledge gained... I really like not being on the list. Best regards, -a- So, I think we have a poor visual here- the donut chart's scale makes the exterior labels a bit misleading and they run together. You can verify your selection by the tooltip that shows when you hover over a slice, or expand the donut chart with the icon that shows up in the top right when you hover on the chart (it says "focus mode"). The R and M are neighboring slices and it is easy to pick the wrong one. I checked the filter and it seems to be working as designed...if that isn't the issue then let me know. 1
neilpilot Posted January 29, 2018 Report Posted January 29, 2018 1 hour ago, jmbaute said: Can you tell me a tail number of the missing plane? I will investigate against source. As I indicated above I think it wasn't missing, just overlooked. N72FG. 1
carusoam Posted January 29, 2018 Report Posted January 29, 2018 John, I think the issue I encountered is the label for the M20M is missing... The line for the M20R is so close to the label for the M22 it appeared that the line belonged to the M22 and not the R... I am using an iPad Air.... Keep up the good work... I have some accident reviews to go through... a necessary, homework assignment to avoid the errors of the past. Best regards, -a-
carusoam Posted January 29, 2018 Report Posted January 29, 2018 https://app.ntsb.gov/pdfgenerator/ReportGeneratorFile.ashx?EventID=20130815X14705&AKey=1&RType=HTML&IType=CA I found an interesting one.... M20R gear up caused by a Battery failure... G1000 system went dark, pilot successfully navigated by iPad... 20/20 hind-sight... click that battery switch and everything will be OK... The pilot was interested in being on the ground, not saving somebody else's plane... I get it... But, I don't get what I am looking for out of the reports, photos, interviews... All I want to know is what Battery failed, Brand and model would be nice... did the charging system kill it? Did I miss something? Or is the NTSB only interested in engine, prop, airframe and pilot details...? Wanting to prevent a similar problem... all I want to know is Battery make and model, and what killed it... Back on topic... John's system has done a great job of organizing the accident reports. The NTSB seems to have put a lot of data in public view including photos and supporting docs. in a quick review of the M20R list. There were VFR into IMC, dark night similar to IMC, IFR In snow that was like dark night, and a whole bunch of going too fast on landing, bounces, and failed go arounds on too short of a runway.... Nice work, John! Best regards, -a-
jmbaute Posted January 29, 2018 Author Report Posted January 29, 2018 8 hours ago, carusoam said: John, I think the issue I encountered is the label for the M20M is missing... The line for the M20R is so close to the label for the M22 it appeared that the line belonged to the M22 and not the R... I am using an iPad Air.... Keep up the good work... I have some accident reviews to go through... a necessary, homework assignment to avoid the errors of the past. Best regards, -a- Glad you're finding it useful; the rendering on mobile devices is not ideal. I'll see if there is a better way to scale this.
Marauder Posted January 29, 2018 Report Posted January 29, 2018 So, I think we have a poor visual here- the donut chart's scale makes the exterior labels a bit misleading and they run together. You can verify your selection by the tooltip that shows when you hover over a slice, or expand the donut chart with the icon that shows up in the top right when you hover on the chart (it says "focus mode"). The R and M are neighboring slices and it is easy to pick the wrong one. I checked the filter and it seems to be working as designed...if that isn't the issue then let me know. You may be able to use the serial number prefix to denote model number instead of the model number. My F model starts with 22-XXXX. The Js I think are 24-XXXX. Sent from my iPad using Tapatalk Pro
bcwiseguy Posted January 29, 2018 Report Posted January 29, 2018 An interesting look. Thanks for sharing this. Some of the data surprises me....like the number of accidents during cruise. It would be nice to be able to see a graph that compares IMC to VMC. I was expecting a larger occurrence of IMC so that was a bit of a surprise.
rbridges Posted January 29, 2018 Report Posted January 29, 2018 I didn't get to spend too much time with it, but it looks pretty cool. Thanks for taking time to do it and sharing!
Marauder Posted January 29, 2018 Report Posted January 29, 2018 Another factor that isn’t shown is the number of flights that made it back without an incident or accident report. It would be nice to have those available to look at. Back in the 1990s when the NTSB made these electronically available, I did an analysis of the M20F accidents. My primary concern was engine failure. It showed that less than 15% were related to mechanical failure (I suspect it is a lot higher because a number were able to successfully get the plane back on the ground). The rest were the usual stupid pilot tricks. Running out of fuel, IMC encounters and landing accidents. Sent from my iPad using Tapatalk Pro
Marauder Posted January 29, 2018 Report Posted January 29, 2018 36 minutes ago, Marauder said: Another factor that isn’t shown is the number of flights that made it back without an incident or accident report. It would be nice to have those available to look at. Like this: https://www.msn.com/en-us/news/us/pilot-lands-plane-on-costa-mesa-freeway-i-saw-an-opening-on-the-highway-and-i-went-for-it-right-away/ar-BBIn7Nn?li=BBnb7Kz
jmbaute Posted January 29, 2018 Author Report Posted January 29, 2018 38 minutes ago, Marauder said: Another factor that isn’t shown is the number of flights that made it back without an incident or accident report. It would be nice to have those available to look at. The NTSB splits these into two categories, accidents and incidents. This report is filtered to accidents. I could probably add another filter to allow you to choose. 1
Freddb34 Posted Wednesday at 06:13 PM Report Posted Wednesday at 06:13 PM During my pre buy yesterday, the AP noted damage history on the form. I looked up N79338 on your list and cannot find anything. Is it possible it was missed or was the AP mistaken? Thanks.
EricJ Posted Wednesday at 06:32 PM Report Posted Wednesday at 06:32 PM 18 minutes ago, Freddb34 said: During my pre buy yesterday, the AP noted damage history on the form. I looked up N79338 on your list and cannot find anything. Is it possible it was missed or was the AP mistaken? Thanks. They may have seen something in the logbooks. You can ask them why they noted damage history. 1
1980Mooney Posted Wednesday at 07:34 PM Report Posted Wednesday at 07:34 PM 57 minutes ago, Freddb34 said: During my pre buy yesterday, the AP noted damage history on the form. I looked up N79338 on your list and cannot find anything. Is it possible it was missed or was the AP mistaken? Thanks. A couple tips: You are responding to a post from 2018 The OP summarized only NTSB "accident" data - that is only serious accidents, injuries and fatalities. It ignores "Incidents" like gear up landings (unless it resulted in a fatality), off field landings, prop strikes, etc. - the vast majority of Mooney insurance claims. Regardless the data in the summary ends in 2018 You mention N79338. It was previously owned by a MooneySpace member and put up for sale here in 2024. Is this the plane? In his "for sale" post the owner said "Some damage history prior to my ownership, apparently repaired satisfactorily. Not always hangared, and lived at KOAK for many years. Was sprayed internally with ACF-50 and maintained by LASAR during this "no expenses spared" period of its life (well, none aside hangarage)." That particular owner acquired it in 2015 so the damage is more than 10 years ago. I bet much longer when you read the logs. Old damage with good repair becomes less and less relevant with time to the point that it likely does not matter on a 60 year old plane. Eventually the only ones that are truthfully "No Damage History" are the ones that don't get flown much.....and that is not good either. I an earlier post you said that you are buying it from your "buddy". He just purchased it in December of last year. He should be able to tell you. He bought it while it was out of Annual. Since he is selling so soon, it appears he bought it to fix it up, get it airworthy and to resell immediately. You need to confirm. 1
Freddb34 Posted 18 hours ago Report Posted 18 hours ago On 10/1/2025 at 3:34 PM, 1980Mooney said: A couple tips: You are responding to a post from 2018 The OP summarized only NTSB "accident" data - that is only serious accidents, injuries and fatalities. It ignores "Incidents" like gear up landings (unless it resulted in a fatality), off field landings, prop strikes, etc. - the vast majority of Mooney insurance claims. Regardless the data in the summary ends in 2018 You mention N79338. It was previously owned by a MooneySpace member and put up for sale here in 2024. Is this the plane? In his "for sale" post the owner said "Some damage history prior to my ownership, apparently repaired satisfactorily. Not always hangared, and lived at KOAK for many years. Was sprayed internally with ACF-50 and maintained by LASAR during this "no expenses spared" period of its life (well, none aside hangarage)." That particular owner acquired it in 2015 so the damage is more than 10 years ago. I bet much longer when you read the logs. Old damage with good repair becomes less and less relevant with time to the point that it likely does not matter on a 60 year old plane. Eventually the only ones that are truthfully "No Damage History" are the ones that don't get flown much.....and that is not good either. I an earlier post you said that you are buying it from your "buddy". He just purchased it in December of last year. He should be able to tell you. He bought it while it was out of Annual. Since he is selling so soon, it appears he bought it to fix it up, get it airworthy and to resell immediately. You need to confirm. Yes, this is the plane I'm getting. We went thru the logs back several years. I didn't think about the fact that the "damage history" could have been simple hanger rash or a runway excursion. I'm pretty confident that the damage was several years ago and the bank was only concerned with damage in the last 5 years. Thanks for the reply! Really looking forward to being part of this community. 1
EricJ Posted 17 hours ago Report Posted 17 hours ago 1 hour ago, Freddb34 said: Yes, this is the plane I'm getting. We went thru the logs back several years. I didn't think about the fact that the "damage history" could have been simple hanger rash or a runway excursion. I'm pretty confident that the damage was several years ago and the bank was only concerned with damage in the last 5 years. Thanks for the reply! Really looking forward to being part of this community. Many older airplanes (i.e., ours) have damage history. It's pretty normal for something to have happened over 40-60+ years. As long as it was properly repaired, there's usually not much consequence after a few years. 2
Recommended Posts