- Joined
- Jun 15, 2017
- Messages
- 16
- Reaction score
- 0
- Age
- 49
- Location
- Spokane, Washington
- Website
- www.underthesundrones.com
Detailed Description of DJI Phantom 4 Pro V1 Malfunction/Crash
Equipment: DJI Phantom 4 Pro Version 1 with GL300E Remote Controller
I am writing to seek expertise and guidance regarding a recent incident involving my DJI Phantom 4 Pro V1 drone. I would like to provide you with a comprehensive account of what transpired, my initial attempts at addressing the issues, and my current situation in the hopes of determining the necessary steps for repair and restoration. Additionally, I would like to understand how to interpret the PARM Log data.
Incident Description: On August 19, 2023, I powered on my DJI Phantom 4 Pro V1 drone, and everything appeared to be functioning as usual. After takeoff, I hovered at an altitude of approximately 7-8 feet to ensure that the drone was flying smoothly and without errors. However, I noticed that the GPS system was experiencing difficulties locking onto the drone's position despite being in "P" mode. This resulted in the drone behaving as if it were in ATTI mode for an unusually extended period, approximately 15-20 seconds. Subsequently, the drone successfully locked onto GPS signals, establishing a home point.
At this point, I initiated an ascent by increasing power using the left stick. It was during this ascent that several error messages appeared on the screen, including "Backward Obstacle Sensing is not functioning," "Exit backward, Forward Sensing system," and "Forward Obstacle Sensing is not functioning." It was at this juncture that I observed what appeared to be a collision or contact between one of the propellers, leading to its breakage. Importantly, I wish to clarify that the drone was operating in an open environment, devoid of proximity to trees, structures, power lines, or any other potential obstacles.
The drone subsequently plummeted to the ground, resulting in observable damage to the left rear arm of the top shell. This damaged arm coincided with the location of the propeller that had broken off (while in flight) as evidenced by photographs taken after the incident. Additionally, an LED cover and a white panel providing access to the landing gear antenna were dislodged in the crash.
Upon further inspection, I noted that while there was no visible external damage to the gimbal, both the gimbal and camera systems were malfunctioning. The camera displayed a fuzzy image on the remote receiver's screen, and the gimbal exhibited erratic movements, failing to initialize and stabilize during the initial power-on sequence of the drone.
Actions Taken: In my efforts to address the situation, I undertook the following actions:
Therefore, I kindly request your professional insights on the following matters:
Thank you for your time and consideration. I eagerly await your guidance and recommendations.
Kind Regards,
Sean Allen
Spokane, Wa..
DAT File Google Drive Link:
PARM Log Google Drive Link:
Google Drive P4P Crash Photos/Data:
Photos: broken propeller while in flight, damaged arm/top shell, screenshot of warnings/errors right before malfunction.
Equipment: DJI Phantom 4 Pro Version 1 with GL300E Remote Controller
I am writing to seek expertise and guidance regarding a recent incident involving my DJI Phantom 4 Pro V1 drone. I would like to provide you with a comprehensive account of what transpired, my initial attempts at addressing the issues, and my current situation in the hopes of determining the necessary steps for repair and restoration. Additionally, I would like to understand how to interpret the PARM Log data.
Incident Description: On August 19, 2023, I powered on my DJI Phantom 4 Pro V1 drone, and everything appeared to be functioning as usual. After takeoff, I hovered at an altitude of approximately 7-8 feet to ensure that the drone was flying smoothly and without errors. However, I noticed that the GPS system was experiencing difficulties locking onto the drone's position despite being in "P" mode. This resulted in the drone behaving as if it were in ATTI mode for an unusually extended period, approximately 15-20 seconds. Subsequently, the drone successfully locked onto GPS signals, establishing a home point.
At this point, I initiated an ascent by increasing power using the left stick. It was during this ascent that several error messages appeared on the screen, including "Backward Obstacle Sensing is not functioning," "Exit backward, Forward Sensing system," and "Forward Obstacle Sensing is not functioning." It was at this juncture that I observed what appeared to be a collision or contact between one of the propellers, leading to its breakage. Importantly, I wish to clarify that the drone was operating in an open environment, devoid of proximity to trees, structures, power lines, or any other potential obstacles.
The drone subsequently plummeted to the ground, resulting in observable damage to the left rear arm of the top shell. This damaged arm coincided with the location of the propeller that had broken off (while in flight) as evidenced by photographs taken after the incident. Additionally, an LED cover and a white panel providing access to the landing gear antenna were dislodged in the crash.
Upon further inspection, I noted that while there was no visible external damage to the gimbal, both the gimbal and camera systems were malfunctioning. The camera displayed a fuzzy image on the remote receiver's screen, and the gimbal exhibited erratic movements, failing to initialize and stabilize during the initial power-on sequence of the drone.
Actions Taken: In my efforts to address the situation, I undertook the following actions:
- I attempted to download flight records in DAT format to discern the cause of the malfunction and crash.
- I made efforts to decrypt the DAT file, which purportedly contains flight records. Regrettably, I encountered challenges in successfully using the DatCon application for this purpose.
- FYI - My laptop is a MacBook Pro and the DAT file is appearing in VLC when I try to access which leads to no data being revealed
- I managed to download flight data via a file called PARM LOG which I am unfamiliar with.
Therefore, I kindly request your professional insights on the following matters:
- Guidance on successfully decrypting the (PARM LOG) flight records contained in the DAT file.
- Recommendations on how to proceed with a comprehensive systems check to identify damaged or malfunctioning components.
- Assistance in determining the specific parts that require repair or replacement based on the aforementioned incident and subsequent checks.
- Any additional steps or precautions I should consider in the repair process.
- An estimate of the feasibility and cost of restoring the drone to operational status, given the described circumstances.
Thank you for your time and consideration. I eagerly await your guidance and recommendations.
Kind Regards,
Sean Allen
Spokane, Wa..
DAT File Google Drive Link:
FLY359.DAT
drive.google.com
PARM Log Google Drive Link:
PARM.LOG
drive.google.com
Google Drive P4P Crash Photos/Data:
P4P Crash Details/Info. - Google Drive
drive.google.com
Photos: broken propeller while in flight, damaged arm/top shell, screenshot of warnings/errors right before malfunction.